Moving to github is the obvious thing to do in order to attract new developers. If this is the chosen path the account username should be something like 'fish-shell' and not contain any other projects so that it can easily be passed on to another person (at a later stage if necessary).
On 08/07/2011 21:49, Christopher Nilsson wrote: > Heya Patrick, > > Nice to see the jolt of energy. :) I > keep wanting to help with this project > as well (fish is cool), but time seems > to fight me. > > As well as the work on github, there's > also the codebase over at gitorious > (https://gitorious.org/fish-shell). > It has seen a bit of bugfix and > feature action from several people, so > it'd be a shame to lose that work. > > An "official" shift to github may be > beneficial, if it hasn't already > happened, since in my mind gitorious' > lack of an issue tracker is a > problem. There's the bug tracker on > the sourceforge account, that also > hosts this mailing list. But we don't > have the keys to that. People can -- > and did -- lodge new bugs, but no-one > (I think) is able to > update/assign/close those bugs. It > would probably help focus feature > requests as well... > > For the mailing list, we do have the > keys to that at least. Over the > history of expiring domains, > spontaneously imploding websites, and > vanishing people, the mailing list has > been the constant. Kudos to > sourceforge and mailman for keeping > that ticking over... Doesn't add to > this discussion, but I thought I'd put > that out there on the archive. :) > > tl;dr: > > * several folk on this list have the > keys to gitorious.org/fish-shell > <http://gitorious.org/fish-shell>, and > this mailing list, so access can be > arranged for those. > * need a bug/issue tracker that we can > actually use. > > - Chris. > > > On 8 July 2011 23:43, Patrick Mc(avery > <patr...@spellingbeewinnars.org > <mailto:patr...@spellingbeewinnars.org>> > wrote: > > "" lets hack!" > > Indeed! > > So again I am the newbie and might > not have things straight.... > > 1)fishshell.org > <http://fishshell.org> is expiring > in September and presumably Axel > won't renew > but Terin Stock has volunteered to > shoulder this > > 2)fishshell.com > <http://fishshell.com> is the > interim site and has code mirrored > from > fishshell.org > <http://fishshell.org> before it > reverted to "it works" > > 3)The wiki was partly lost in the > transfer but Martin Bähr has a copy > from August 2010 > > 4)There is some development being > done on github but the site does not > currently point there > Please correct false statements... > > > > So I don't actually know who is in > control of the mailing list? Is it > Terin? He is in control of > fishshell.com > <http://fishshell.com> right? What > is fishshell.com > <http://fishshell.com> > running on in terms of a framework > or is it all static content? Is there > anyway to help Terin with the > site? once we have a wiki again I > would > like to contribute but setting up > the wiki may or may not be that > simple. > > Attachments are usually frowned > upon on mailing lists but this is a > small one. What if I started a > block level SVG diagram of code > base and > mailed it to the list? If people > can install Inkscape then they could > mail corrections back to the list. > Eventually we could form a working > diagram of the code base, would > this not make it easier to get new > developers? > > If the wiki is going to take > sometime, could I start a Google > doc and > invite everyone to edit it and we > could build up the knowledge base > again? If I could get the old wiki > from Aug/2010 then that would be good. > > Any other suggestions? > > > P.S > "and list want needs to be done" > I meant "list what needs to be > done" in my last post. As a native > English speaker I have no defence > for my poor spelling. It is the > motivation behind my domain > SpellingBeeWinnars.org, sorry > about that > > > ------------------------------------------------------------------------------ > All of the data generated in your > IT infrastructure is seriously > valuable. > Why? It contains a definitive > record of application performance, > security > threats, fraudulent activity, and > more. Splunk takes this data and makes > sense of it. IT sense. And common > sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Fish-users mailing list > Fish-users@lists.sourceforge.net > <mailto:Fish-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/fish-users > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > > > _______________________________________________ > Fish-users mailing list > Fish-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fish-users ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
