> First, who is in the association? I don't see it as an exclusive club, > but the simple task of making a list of maintained packages compatible > with this Not Really Named stack would be quite useful to people.
Agreed. What we want is a way to have some cross-marketing possibilities, a a way to say that we're organized to work together, and a way to encourage people to write code with "the stack" in mind. > We should have some badge or link of some sort, and agree on a place to > put it (generally) -- side bar, foot of the page, both, an icon in the > top right... there's several options. I'd be open to something more > prominent than just a little badge. Those stop-poverty icons in the > corner of some pages look nice to me. Damned if I can find one at the > moment. This makes sense to me too. > From there we might want to consider sharing services and > infrastructure. Sphinx is looking nice, and if we all started using it > for docs then we might have some opportunity to do more sophisticated > things using it (e.g., to cross link). I really like this idea -- one of our core issues as a stack is documentation. Django, and Rails both do better at the documentation game than we do, and one of the core issues I would like to see us address --as a group-- is documentation. If we could setup some standards, and make Sphinx do interlinking of documentation, I see this as a huge benefit of the association and a very good thing for our users. > Shared search could be useful. Also agreed. Google lets you make a branded search now, so this infrastructure is more of a social and organizational issue than a technical one -- but it's something we really should make happen. ;) > If we want to setup stuff like IRC logging, that can easily be managed > once. The wiki situation is also kind of a mess for everyone, and wiki > content is the content most likely to be cross-library. This makes a lot of sense too. We'd started thinking about a shared python web projects wiki a year ago, and it seems like an idea worth revisiting. Many times documentaiton grows up in the wiki and turns into official docs over time, so it seems to me that we'll want to continue to ask people to use ReST as the markup language in the wiki. > These steps seem realistic to me. Right now I don't believe anyone but > TG has much money to manage, so I don't have any need for any structure > like that. Yea, I think the organization of the community is more important than the money issues -- on the other hand we might have more money if we had a good clean way for people to make donations to the stack. I know the TG list has had several requests for a donation link -- which we've not done because it would require having some kind of more organized structure. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
