sprint planning

[Mark Ramm]

I'm planning to try to put a bunch of tasks into Trac+the
SprintOrganization wiki this weekend, so that we have a good list of
thngs to work on next week.

I'd like to have a few more things finalized this weekend in terms of
the TG2 codebase too:

* Validation (I think this just needs adding)
* a working version of paster shell for working with models interactively
* a slightly updated test infrastructure and some sample tests

I think we should create a TG2 sprint branch towards the end of the
week, and I think we'll need to give out SVN access to that branch to
some people. Perhaps we can create a couple of generic accounts and
pass out usernames/passwords durring the sprint. Alternatively we
could wait for the sprint days and create logins for people on a
per-user basis.

What do you all think?

--
Mark Ramm-Christensen
email: mark at compoundthinking dot com
blog: www.compoundthinking.com/blog

[Kevin Horn]

On Jan 4, 2008 8:47 PM, Mark Ramm <mark.mch...@gmail.com> wrote:

I think we should create a TG2 sprint branch towards the end of the
week, and I think we'll need to give out SVN access to that branch to
some people.   Perhaps we can create a couple of generic accounts and
pass out usernames/passwords durring the sprint.   Alternatively we
could wait for the sprint days and create logins for people on a
per-user basis.

What do you all think?

I think individual passwords would be better.  Would help with tracking contributions.

Kevin Horn

[percious]

Sign up:
I'm probably going to regret this, but I think I will take on the 20
Minute Wiki.
We need that working in the docs the most, IMO.
I wouldn't mind working on tg.url either, since I have a pretty good
understanding of the dispatch.
I wouldn't mind working on validation with Alberto, but it appears he
has cleaned that up, pre-sprint.

Just point me where you think we need the most work. DBSprockets is
going to sit and fester for a week.


About access:
per-user is ok, but I don't know if everyone needs to sign the TG
contributor agreement.
It seems like sprints like this should be precluded, and that process
seems heavy-handed,
given the number of developers.


-chris

On Jan 4, 8:59 pm, "Kevin Horn" <kevin.h...@gmail.com> wrote:

[Mark Ramm]

> About access:
> per-user is ok, but I don't know if everyone needs to sign the TG
> contributor agreement.
> It seems like sprints like this should be precluded, and that process
> seems heavy-handed,
> given the number of developers.

The thing that the agreement says's important is that you prommise not
to throw stuff legal for us to use into the repository ;)

My plan is just to ask people to throw an e-mail agreeing to the text
of the agreement to the list, and I'll send them svn credentials.
Hopefuly this will be painless and go really quick.

[Mark Ramm]

> Sign up:
> I'm probably going to regret this, but I think I will take on the 20
> Minute Wiki.

I would wait on this, as it would be a good place for someone learning
TG2 to start, and there are a couple of people who've already
expressed some interest in this.

> We need that working in the docs the most, IMO.

Agreed, we need a basic TG2 tutoral document before we can even
consider a release, and there is no such thing yet.

> I wouldn't mind working on tg.url either, since I have a pretty good
> understanding of the dispatch.

This would be a big help, because it's used in the 20 min wiki. ;)

> I wouldn't mind working on validation with Alberto, but it appears he
> has cleaned that up, pre-sprint.

Well, I think we are 80% of the way we need to go on validation, but
what we have is "good enough" for now. But this is one place where it
would be nice to nail down the API sooner rather than later.

> Just point me where you think we need the most work. DBSprockets is
> going to sit and fester for a week.

Well, one thing we may want to do is create a DBSprockets test project
and tutorial, and it may be that someone other than you should work on
that if there's anybody available. ;)

--Mark Ramm

[percious]

> Well, one thing we may want to do is create a DBSprockets test project
> and tutorial, and it may be that someone other than you should work on
> that if there's anybody available. ;)
>

I did that last night.... I probably could make it a stand-alone egg,
but I don't want to clutter up PyPI.

http://code.google.com/p/dbsprockets/wiki/DBSprocketsAPI

(about 1/2 way down.)

[Paul Johnston]

Hi,

>>I'm probably going to regret this, but I think I will take on the 20
>>Minute Wiki.
>>
>>
>I would wait on this, as it would be a good place for someone learning
>TG2 to start, and there are a couple of people who've already
>expressed some interest in this.
>
>

Yes, I've got one person lined up for doing this at the York sprint.

Paul

[gas...@gmail.com]

Hi,

I wish we could do something like

records = model.Movie.select()
DataGrid(records) # show table

DataForm(model.Movie) # show input form

as they do
http://mdp.cti.depaul.edu/examples/default/orm

If possible I want to integrate this function into TgCrud.

[Christopher Arndt]

Hi Mark,

could you (we) maybe write up some short instructions on what sprint
participants should do on Saturday when they start working?

Please bear in mind that some of us are in European time zones and may
start considerably earlier than you in the US.

Something along the lines of:

1) Check http://docs.turbogears.org/SprintOrganization for any new
information

2) Go to #turbogears on irc.freenode.net and say hi

3) Go to the turbogears trac and get an account (if you haven't got one
yet).

4) Check http://trac.turbogears.org/query for tickets* you can work on.

5) See http://trac.turbogears.org/timeline for what has been done by
whom in the last few days.

6) Pick a ticket and assign it to yourself. If necessary, open a new
ticket first (maybe discuss it on IRC first).

7) Work away and have fun!

Anything else?

Chris

* BTW: How are sprint tickets identified? Is there a special ticket
keyword one can search for?

[Mark Ramm]

I was planning to add this kind of instructions to the
SprintOrganization page, and sending e-mail here about it.

We may want to change the IRC topic to point to the Sprint page too.

The other task of the day is to try to get some basic developer docs
written that explain how things work in TurboGears 2.

--Mark

--

[Lee McFadden]

On Jan 11, 2008 2:18 PM, Mark Ramm <mark.mch...@gmail.com> wrote:
>
> We may want to change the IRC topic to point to the Sprint page too.
>

I'll do that right now so it's set up ready for tomorrow.

--
Lee McFadden

blog: http://www.splee.co.uk
work: http://fireflisystems.com
skype: fireflisystems

[Christopher Arndt]

Lee McFadden schrieb:

> On Jan 11, 2008 2:18 PM, Mark Ramm <mark.mch...@gmail.com> wrote:
>> We may want to change the IRC topic to point to the Sprint page too.
>>
>
> I'll do that right now so it's set up ready for tomorrow.

BTW: do you think you could get the irclog.turbogears.org bot up running
again for tomorrow?

Chris

[Lee McFadden]

On Jan 11, 2008 2:45 PM, Christopher Arndt <chris...@web.de> wrote:
>
> BTW: do you think you could get the irclog.turbogears.org bot up running
> again for tomorrow?
>
> Chris
>

Yes, I'm working on that now. I hadn't checked in on the site in a
while as arkivobot is there when I log into IRC, but it seems someone
else is running an arkivobot and I can't to find the front end.

If any of you know who it is, please let me know. I'm more than happy
to help someone get arkivobot up and running, especially if they
intend to work on fixing bugs and/or adding features. The project has
been sorely neglected recently and I haven't had the time to keep it
in 100% working order (although I still have big plans scrawled in a
notepad).

Lee

[Max Ischenko]

Hello,

On Jan 5, 2008 4:47 AM, Mark Ramm <mark.mch...@gmail.com> wrote:

I'm planning to try to put a bunch of tasks into Trac+the
SprintOrganization wiki this weekend, so that we have a good list of
thngs to work on next week.

I'd like to have a few more things finalized this weekend in terms of
the TG2 codebase too:

* Validation  (I think this just needs adding)

Can anyone elaborate about what's need to be done?

I'd like to help with this one.

I am currently develop a Pylons app and I'm far from happy with its validation helpers. So I'd be happy to do some work for TG2 here and may be then be able to re-use it (or at least experience gained) in my Pylons app.

Max.

[percious]

Feel free to open an issue on http://dbsprockets.googlecode.com or
post on the dbsprockets
board. I think it would be best to keep this thread more TG2
oriented, even if dbsprockets is part of tg2.

I wouldn't mind doing some Graffle documentation for the website
tomorrow. I'm only going to be sprinting
8-11:30, so I sort of need something that is pretty easy to tidy up in
4 hours. I will take a look at tg.url()
if I have time tonight, however.

-chris

On Jan 11, 12:47 am, "gaso...@gmail.com" <gaso...@gmail.com> wrote:
> Hi,
>
> I wish we could do something like
>
> records = model.Movie.select()
> DataGrid(records) # show table
>
> DataForm(model.Movie) # show input form
>

> as they dohttp://mdp.cti.depaul.edu/examples/default/orm

[Mark Ramm]

So we've updated the current validator in tg2, but it's still pretty basic.

There's a ticket for this:

http://trac.turbogears.org/ticket/1636

But if you have some good ideas on how validation could be improved (I
know you've spent some time with newforms, so if there are some ideas
from that that make sense for us, I'd love to hear about it.

Fell free to update that ticket with suggestions.

--Mark Ramm

--

[percious]

The problem I ran into with the current tw/tg2 validator was that you
were not able to feed it a callable (as you were in TG1). I ended up
copying the current validator and modifying it for my purposes. I
thought having a function which you could pass into the validator was
a reasonable way of handling the miriad of ways a form may be created.

-chris

On Jan 11, 12:29 pm, "Mark Ramm" <mark.mchristen...@gmail.com> wrote:
> So we've updated the current validator in tg2, but it's still pretty basic.
>
> There's a ticket for this:
>
> http://trac.turbogears.org/ticket/1636
>
> But if you have some good ideas on how validation could be improved (I
> know you've spent some time with newforms, so if there are some ideas
> from that that make sense for us, I'd love to hear about it.
>
> Fell free to update that ticket with suggestions.
>
> --Mark Ramm
>

> On Jan 11, 2008 10:44 AM, Max Ischenko <ische...@gmail.com> wrote:
>
>
>
> > Hello,
>

[Mark Ramm]

This makes sense, if you want to push your changes back into TG, I
think this is something that should be handled in TG itself.

[percious]

I can probably handle that. One of the things that makes the water
muddy (i believe) is that TWidgets are callable themselves, but maybe
Alberto can comment more on it.

-chris