changes and centralizing

[Christopher Johnson]

Hi folks,

Just wanted to let you all know I have been talking with Emiliano lately about managing the agilito open source project. As he is currently the most active member, I wanted to make sure we supported him and his initiative with agilito. Here are some of the ideas we are working on to keep agilito moving forward:

- Making Emiliano an project owner (google code perms) and also promoting his participation as working on trunk, advising us of what he does (but no need to request review of patches, as it isn't happening in a timely fashion).
- Move things to Google Code for issue tracking, feature requests. GetSatisfaction has been an under-whelming experience and just spreads things out. Since we are primarily developer-oriented at this point, makes sense to stick with developer tools. I'll be adding some notes to GS shortly.

We also encourage those in the community to communicate about how they want to contribute to the project. Emiliano is excited to work with others and would love to collaborate with anyone available to help.

If you have additional ideas or questions, please let us know!

Thanks!

-chris

--
Cofounder and CEO
ifPeople - Innovation for People
www.ifpeople.net
t: 678-608-3408 x16

[Emiliano Heyns]

We currently have a few ways to get my stuff brought back to Agilito:

* We have the google site administrator reset our repo, and I
svnsync the air repo back to agilito. Plus side, this retains full
history on each individual file. Down side: it will take a few days
before the admins get around to it, and any change that happens in the
mean time (including to the wiki) will be lost.
* I issue an svn delete against the trunk directory and import the
current trunk from air. Plus side: can be done tonight, and the wiki
is untouched. Down side: file history breaks.
* Someone studies svk and finds out how to replay the air commits
to the agilito repo. Theoretically it can be done. In practice, I
tried, and the results can be seen in te Agilito repo. Plus side: full
history is retained. Down side: this is going to take time.

Cue rant about how svn makes distributed development miserable.

Regards,
Emile

[Emiliano Heyns]

On Feb 14, 9:31 pm, Emiliano Heyns <Emiliano.He...@gmail.com> wrote:
> We currently have a few ways to get my stuff brought back to Agilito:
>
>     * We have the google site administrator reset our repo, and I
> svnsync the air repo back to agilito. Plus side, this retains full
> history on each individual file. Down side: it will take a few days
> before the admins get around to it, and any change that happens in the
> mean time (including to the wiki) will be lost.
>     * I issue an svn delete against the trunk directory and import the
> current trunk from air. Plus side: can be done tonight, and the wiki
> is untouched. Down side: file history breaks.
>     * Someone studies svk and finds out how to replay the air commits
> to the agilito repo. Theoretically it can be done. In practice, I
> tried, and the results can be seen in te Agilito repo. Plus side: full
> history is retained. Down side: this is going to take time.

Then there's always doing loads of 'svn diff's and reapply those
patches. Which seems to have worked. The repo should be up to speed
now, and my local working areas are pointed towards agilito once more.
Here's to more interactivity within agilito!

Emile

[Christopher Johnson]

Yeah!
I will ask about if we can carve out some space on our dev server for a demo area...would love to see the latest in action!
-c

Emile