Hi, I see a long list of website issues being posted to this list. The thing that concerns me is would Kenneth and his team be able to track everything via this mailing list ? A mailing list is not meant for posting and following up such issues. It can at best be used as a discussion forum . I don't think it is a good idea to continue posting issues to the list. Can a Trac or similar issue tracker be added to the site quickly to take care of this ? Otherwise, we could simply create a google code project and use it only to track issues without using it to manage the code. Of course, the negative of this is that this can become a mini project of its own and we could get side-tracked and lose focus. However considering the amount of issues being reported, this seems to be happening someway in the mailing list itself. We need to iron out all major issues with the website and templates/CSS etc within 2-3 weeks max and open it up by June end at least. Otherwise we could get derailed. If not a tracker, at least a progress report should be maintained somewhere which lists all issues and its criticality, status etc. It could even be a Wiki on the python.org site. However without tracking these issues, I don't see we are going anywhere. Regards, -- -Anand
On Sun, May 31, 2009 at 11:57 AM, Anand Balachandran Pillai <abpillai@gmail.com> wrote: [..]
We need to iron out all major issues with the website and templates/CSS etc within 2-3 weeks max and open it up by June end at least. Otherwise we could get derailed. [..]
That's too late. We need to get this thing out in early June. If it's ready only by early July, we'll have just 2 month (July and August) to take care of sponsorships, CFPs and other logistics. I think that will be too tight. Without the site, we can't do any publicity or call for CFPs and that's why I'm pushing for it. I assume that Kenneth and his team is harvesting the bug reports from the mailing list and keeping track of them. I suggest that we put a deadline (say 7th June) and then if the site is not completely functional and ready for release by then, we fall back to using a bunch of static pages and an authenticated wiki (similar to the PyCon UK site). It will be a little more work but things will move. As for the registration, we can develop a tiny app which shoves user information into a database and keeps a list so that we can use it to charge only early bird fees for the people who register early. Talk scheduling and stuff must be handled manually (and I don't think it will be *that* hard). Opinions? -- ~noufal
Anand Balachandran Pillai wrote:
Can a Trac or similar issue tracker be added to the site quickly to take care of this ? Otherwise, we could simply create a google code project and use it only to track issues without using it to manage the code.
+ 1. I remember there was a Trac site when it was used for FossConf firs time. If it is available, we can use it. Else a new Trac site can be put up which can be both used to report bugs as well as tracking development and future todos. -- With Regards, Parthan SR "technofreak" GPG Key 2FF01026 Fingerprint 5707 ECBD 8D8D 8E6E 28F8 DFA5 938B D861 2FF0 1026 Weblog http://blog.technofreak.in
Can a Trac or similar issue tracker be added to the site quickly to take care of this ? Otherwise, we could simply create a google code project and use it only to track issues without using it to manage the code.
+ 1. I remember there was a Trac site when it was used for FossConf firs time. If it is available, we can use it. Else a new Trac site can be put up which can be both used to report bugs as well as tracking development and future todos.
or use launchpad.net.
participants (4)
-
Anand Balachandran Pillai -
Anand Chitipothu -
Noufal Ibrahim -
Parthan SR