On Fri, Apr 19, 2013 at 12:02 AM, Andrej N. Gritsenko <[email protected]> wrote: > Hello! > > Sharon Kimble has written on Thursday, 18 April, at 4:58: >>On Thu, 18 Apr 2013 11:07:02 +0800 >>PCMan <[email protected]> wrote: >>> For me, options are: >>> 1. Migrate to Google code: >>> Pros: very simple UI, fast, git repo, issue tracker (no category, only >>> labels), wiki pages, file release management. Can use google groups >>> for discussions. >>> Cons: since Google code is not related to Google+ or mobile, the >>> service might be terminated unexpectedly someday. That's the fate of >>> Google services that do not make money. > > Google code doesn't use SSH therefore password may be send in plain > text over HTTP(S), that may be considered a security hole. > >>> 2. Migrate to github: >>> Pros: fast, nice git repo management. >>> Cons: no issue traker, no mailing list, no other things our projects >>> will need. Only the git repo is good. > > Well, it is not so good. The git repo browser at github is kinda > bloated as well. It is otherwise bloated than Allura but still it is, > for example there is no 'shortlog' commit list with easy links, it is > somewhat giantic (in comparison with GitWeb shortlog) and requires few > pages loading to get what is available with single click in shortlog. > >>> 3. Keep sourceforge and move the git repos to github. >>> Pros: still having the issue trackers and mailing lists, and we can >>> use better git code browser and others. > > No, only mailing lists are available but I'm not sure if it's > available without a project or we should have non-functional project > mirrors at SF for that. The issue tracker is hardly usable for us in > Allura and that is the main problem. So this is not an option. > >>or 4. Self-host, with your own git repo, your own bug tracker, and >>mailman for your mailing lists. Yes, it could be tough to set up but >>the benefits in the long term would be great. > > I have skills to setup those things so I could offer my help. And I > think this is the best choise but it brings up hosting question. > >>Sharon. > > With best wishes. > Andriy. >
The benefit of free hosting is quite obvious. Minimal maintanance, proper backups, download mirrors, minimal downtimes, stable and reliable bandwidth, free of charge, and everything works out of the box. Though we can have our own hosting, if possible, using a free one is better. Regarding to bug trackers, bugzilla is quite complete, but its UI is really too bad for ordinary end users. It's a pity that Google is not available in some countries. It came to my mind that there are two sourceforge derivatives. http://savannah.nongnu.org/ http://developer.berlios.de/ Both are derived from the very old sourceforge.net code. So they look very similar to the original old sourceforge.net many years ago. They provide everything now we're using from sf.net. Moving away from sf.net not only means we need to get a new bug tracker and git repos, but it also means that we need to recreate all of the user accounts and settings the permissions properly. If possible, migrating old bugs to the new systems. That's quite a lot of work which I'd like to avoid. Can we submit support requests to sf.net staff asking for some help? I did not see any options in the new admin UI to turn off the stupid "new features". I don't like the new UI, either, but I'd like to avoid migrating everything to minimize the effort needed, if possible. ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Pcmanfm-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pcmanfm-develop
