Trac Sprint - PyCon 2009
John Hampton
Once again, we will be having a Trac Sprint at PyCon 2009[1].
A page has been setup on the PyCon site for the Trac Sprint.
http://us.pycon.org/2009/sprints/projects/trac/
Please visit the page. If you will be at PyCon and are staying for the
sprints, please join us and add your name to the page.
Additionally, regardless of whether you'll be attending the sprints,
please add suggestions.
Thanks.
-John
Olemis Lang
>
> Once again, we will be having a Trac Sprint at PyCon 2009[1].
>
On Mon, Feb 23, 2009 at 10:56 AM, John Hampton <paco...@pacopablo.com> wrote:
> Olemis Lang wrote:
>> On Mon, Feb 23, 2009 at 8:56 AM, Yunior Armando Hernandez Andrade <yaher...@estudiantes.uci.cu> wrote:
>
>>> Does anyone knows where can I submit the functionalities I would like
>>> developers to implement for the trac's sprint?
>
[...]
> the PyCon wiki page
>
IMO this is the best place ... or even trac.edgewall.com, specially if
both of them are kept up to date ... ;)
> Additionally, you can send the ideas to me or to the list.
... optionally, but I think it is very nice to have all the requests
in PyCon wiki since the sprint will be carried out in the context of
this event.
> However,
> please use the following thread:
>
> http://groups.google.com/group/trac-users/browse_thread/thread/4caa3525341986ff#
>
That's why I'm replying here ... I hope you dont mind ... ;)
> Or create a new thread. However, please do not reply to an existing
> thread and change the subject to create a new thread. Doing so tends to
> bury the thread inside an unrelated one.
>
+1
>> Another Q ... is this only about trac core ? ... or is it about trac
>> core + plugins ?
>
> The sprint is open to anything Trac related.
Wow ...
> You're welcome to suggest
> anything you'd like.
:)
> However, we always have more suggestions than we
> can accomplish,
Understood ...
> so what actually gets done is up to those that actually
> participate.
>
;)
> Additionally, if you're not going to PyCon, but may have some time to
> sprint, we will be on #trac throughout the sprint.
>
Great news !!! I hope I'll can join you there, and sprint together ... :)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
John Hampton
<snip>
>> Additionally, you can send the ideas to me or to the list.
>
> ... optionally, but I think it is very nice to have all the requests
> in PyCon wiki since the sprint will be carried out in the context of
> this event.
Indeed. I will be keeping both wiki pages up to date. So whichever
medium is easiest.
-John
Jorge Vargas
Hello John, I'll be at pycon this year (my first!) and I'll love to
try to fit some time to work on trac. I'll add myself to the page one
of these days when I plan my pycon days (I'll be there all 10 days)
I'll really love if people could work on
multi-project support (#130), ticket progress bar (#1084, a long time
favorite of mine I never got around implementing), ticket comment
edition (#454), bulk ticket changes (#525), etc.
And lets not forget ticket dependencies (#31) ! very important!
if you search a little you will know why this is very important for
the greater trac community.
On a more personal request I'll like too see a little bit more of work
on the trac 0.12 multirepo branch.
PS: I'll add this to the pycon page soon, unless people don't accepted it :)
John Hampton
> Hello John, I'll be at pycon this year (my first!) and I'll love to
> try to fit some time to work on trac. I'll add myself to the page one
> of these days when I plan my pycon days (I'll be there all 10 days)
Welcome! I added your name to the page but left off how many days you
would be sprinting. Feel free to update that with "4 days" anytime you
want :)
> I'll really love if people could work on
>
> multi-project support (#130), ticket progress bar (#1084, a long time
> favorite of mine I never got around implementing), ticket comment
> edition (#454), bulk ticket changes (#525), etc.
>
> And lets not forget ticket dependencies (#31) ! very important!
Well, you sure managed to pick some of the controversial ones :) Work
on any and/or all of those is welcome.
Multi-project and ticket dependencies are the two biggies. Be prepared
for some vibrant discussion on those.
Ticket progress bar and bulk ticket changes should be able to be done as
plugins. I know there is the batch modify plugin out there, though I've
never tried it. Getting both of those features to work nicely as
plugins is definitely the first step to getting them eventually included
in core[1]
Ticket comment editing could also start life as a plugin. Though I
imagine that it would be slightly cleaner in core.
Anyway, glad to have any help you can give us.
-John
P.S. Ping us in #trac when you're at pycon
[1] If ever. While the ticket progress is neat, I'm not sure it ever
really belongs in core.