webERP Forum
Sourceforge subversion problem - Printable Version

+- webERP Forum (http://www.weberp.org/forum)
+-- Forum: webERP Discussion (http://www.weberp.org/forum/forumdisplay.php?fid=1)
+--- Forum: Development Discussion & Specification (http://www.weberp.org/forum/forumdisplay.php?fid=10)
+--- Thread: Sourceforge subversion problem (/showthread.php?tid=8066)

Pages: 1 2 3 4 5 6 7 8 9 10 11


RE: Sourceforge subversion problem - TurboPT - 03-06-2018

Looks nice, so far!

I'll give it a better review tomorrow.


RE: Sourceforge subversion problem - afcouling - 03-06-2018

(03-06-2018, 12:13 PM)phil Wrote: I've been starting to write up a bit of a how-to on git on the webERP-team git wiki

https://github.com/webERP-team/webERP/wiki

I am hopelessly under-qualified to do so - but thought I might be able to write up based on my recent learning.... only the embryo of a useful document so far. However, I am not completely sure I am correct and if someone could take a look/embrace and extend that would be great.

Hi Phil,

Good work!
I hadn't spotted the wiki functionality until now.
It certainly seems like an appropriate place to store development guides/info.
I'm happy to contribute, and have a couple of ideas.
I'll have a proper look later today.

Andy.



RE: Sourceforge subversion problem - TurboPT - 03-07-2018

Phil, I have applied a few minor edits to the wiki:

1. Added an image to indicate the fork button location
2. Placed the git command line inputs into code sections (and the chmod command too)
3. Other edits, such as white space to improve readability, etc.

That is a nice wiki to have there, as I (among others) will surely add other information/details later.


RE: Sourceforge subversion problem - TimSchofield - 03-08-2018

Sourceforge has the ability to add git repositories as well so it might be advantageous for someone with access to push the repository there and keep it up to date (easy enough to do with a script) so that anybody looking there can get the code


RE: Sourceforge subversion problem - TurboPT - 03-08-2018

Tim,

I had thought about that, but given the hassle(s) experienced with the SVN at SF (low support, and other site issues there), it seems that it would be better to add links to the new github location instead? ... but that's only my opinion. However, there could be other aspects that I'm not considering.


RE: Sourceforge subversion problem - TimSchofield - 03-08-2018

The thing is that with Git you have the entire repository with all the history on you local machine as do I and others. If the sf repository got corrupted you would just delete it and push a new one out.
It is the beauty of distributed version control. There is no central repository to get corrupted. I read a post from Linus Torvalds once saying he never backs up his work because so many people pull his code if his computer was lost or destroyed he would simply pull it back from one of them


RE: Sourceforge subversion problem - afcouling - 03-09-2018

(03-08-2018, 05:46 AM)TurboPT Wrote: it seems that it would be better to add links to the new github location instead?

I'm with you on this one Paul.
Lets keep it simple, and add a link from SF to GH, rather than have a copy of the code in SF.
To have a the link and a copy of the code in SF could be confusing to others.
If we agree this is the way forward, then might be best to delete the SF repo.

As I write, SF is down again.

Andy.



RE: Sourceforge subversion problem - phil - 03-10-2018

I am with you chaps too ... I renamed the code "See GitHub" in sourceforge and deleted the subversion repository so there is no confusion


RE: Sourceforge subversion problem - afcouling - 03-10-2018

Thanks Phil.
From my login, the 'Code' tab is no longer visible on SF.

Andy.


RE: Sourceforge subversion problem - TurboPT - 03-11-2018

Andy/Phil:

I'm not 100% sure of this aspect, but I'm guessing that removing the SVN repository at SF made the code tab go away?

Anyway, I added a "webERP at GitHub" tab (an external link) at SF.

If some other phrase would be more desirable, let me know.