On Mon, 30 Jun 2014 08:01:51 -0400, Brian Hinz wrote: > > The source for the builds has been coming from the github repo since last > week. I suggest leaving them where they are for now, since the URL makes > no reference to sourceforge. >
http://tigervnc.sourceforge.net/tiger.nightly/ ^^^^^^^^^^^^^^^ :) But it can stay there for now. At least whilst everything else is sorted out. Btw, where did git2719 come from? Normally people use the first few characters of the commit id in pre-release builds like that. Makes it easy to map to which source code was used. And since I see you've already made a commit to git, I have some suggestions: - Remember to write a single line by itself at the start of every commit. A lot of the git tools assume this convention for neat log output. E.g.: Foo foo foooo foo fooo foooooooooooooooooooooooooo More detailed stuff here spanning over as many lines as you feel is necessary to make everything clear. - I think we should avoid committing directly to the repo, at least to start with. Instead make a fork and commit to your private repo (like anyone else would do). Then merge things back when you have something new. It will allow us to practice a good merge flow, and it can avoid pushing mistakes to the main repo. - Are your build scripts already in contrib? Otherwise I suggest adding a secondary repo to tigervnc with the build magic. > > Anyone got any experience of what's appropriate to with the old project > > page in a case like this? Putting some kind of notice and putting as > > much as possible in read-only state is the minimum effort I'd say. But > > should we do more? Actively break something to make sure people notice? > > Remove things? > > > > I'm certain that I've seen README's on SF download pages that redirect > people to github, etc. I'll see if I can locate an example. > I found some projects that changed the heading somehow: https://sourceforge.net/projects/webpa/ https://sourceforge.net/projects/htop/ I think we should do something like this: - Add a notice like those two projects. - Nuke the wiki (it was poorly converted from mediawiki anyway) - Nuke the bug tracker (I don't think it has much historic value anyway) - Maybe add a final commit that updates our README with a notice. Rgds -- Pierre Ossman Software Development Cendio AB http://cendio.com Teknikringen 8 http://twitter.com/ThinLinc 583 30 Linköping http://facebook.com/ThinLinc Phone: +46-13-214600 http://plus.google.com/+CendioThinLinc A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
