Moving Forward

[Paul]

Hello everyone,

My name is Paul Shoemaker. I am a software developer currently
utilizing the LAMP stack just as the many who are interested in this
project probably are as well. I am currently employed and the team I
am apart of is beginning to expand and integrate best practices into
our design methodology which includes such things as continuous
integration, unit testing, etc. We manage a relatively large code
base that is beginning to expand quickly and on many different fronts
with many different initiatives. As such, the ability to manage that
expansion efficiently while developing only the highest quality code
has become a significant priority for us. This is where Xinc has come
in to help us manage what is quickly becoming a larger project
(potentially spawning several sub projects). As a consumer of open
source software it has always been my desire to be able to give back
in some tangible way so, in that vein, I saw that this project was
stagnating a bit and sought to help. I contacted Arno and he has been
so kind as to add me to the admin group of the project on google code
so that we, as a community, can begin to move forward. No doubt, in
using Xinc you have found it to be a remarkable piece of software but,
none the less, lacking in certain areas. This is where I hope the
community (including myself, naturally) will come in to step forward
and fill in the gaps.

After seeing that there were more than a couple of status questions in
this group, I decided to create a new post rather than replying to
those individually. Those of you who have expressed interest in
contributing to Xinc in the past, please reply to this thread with a
quick intro and what you would like to contribute. Everyone is
welcome to participate regardless of skill level (we will find
something for you to do, I promise).

I will be spending the majority of my time learning the internals of
this project and begin contributing a fix or two given the tickets on
the google code site. If there is anything you would like to see
implemented or specific bugs that you have identified, please log a
ticket on the google code site with as much information as you can
provide.

In the event that there are those of you out there who have made
modifications to the code base on your own to implement features, I
would love to take a look at those and perhaps merge them into the
trunk once a full review has been made.

I look forward to working with you all to build something interesting.

Paul

[Jamie Talbot]

Hi Paul,

Welcome! I'm a committer on the project, but haven't had as much time
as I'd like to contribute. I'm a professional PHP developer and am
comfortable with the codebase, but don't have the time to organise the
project in the way that Arno was doing. It will be great to have
someone on board who can do that. I'm very happy to take on requests
and continue working on the code. If you look at the Xinc-Dev group,
a tentative roadmap was in place with general goals for the future -
that might be a good place to start. Look forward to working with
you!

Cheers,

Jamie.

--
http://jamietalbot.com/

[Paul]

Hi Jamie! Nice to meet you! I look forward to working with you. I,
too, have limited resources at the moment but my time will free up
quite a bit in the next few weeks. Until then I'll spend my time
learning the code base a bit and picking up where Arno left off with
the tickets that have been logged.

Yes, I see that roadmap now. Am I correct in stating that Priorities
1 and 2 are feature complete as of version 2.0.1? This would be
something worth revisiting.

Paul

[Daniel Cousineau]

Hey Paul,

I was a contributor as well but same as Jamie I got caught up in my "regular" life (finishing up last semester of my undergrad).

I'm not entirely sure about the completion of any milestones, I remember we had put together a tentative roadmap and right around when we settled on it Arno had to be hospitalized and unfortunately all the commiters got distracted by their personal lives.

I know originally I had plans to help do a redesign on Xinc, but I don't know if we want to readjust the roadmap or not. I should be available to help out but I can't guarantee anything since I've already "flaked" once :(

Thanks and Gig 'Em!
Daniel Cousineau
http://www.toosweettobesour.com/
http://www.linkedin.com/in/dcousineau
dcous...@gmail.com

[Torsten]

Hi Paul,

My namei st Torsten Zander and I would like to help the project as far as
I can.
I am not familiar with the code but but starting with some small tasks
I shouldn't be
a problem getting inti it, since the code is well written.

Torsten


Torsten Zander
Webentwicklung & Consulting

Hildastr. 3 Email: in...@tzander.de
65189 Wiesbaden Tel: +49611-1747870



2009/4/6 Paul <apsho...@gmail.com>:

--
Viele Grüße
Torsten

[Paul]

Hello and welcome!

I think I would like to begin by working through the issues starting
with critical bugs / complaints and moving into feature requests. I
am going to go through the issue list and examine each one to confirm
that they are indeed defects (and not feature requests) and then
prioritize them. Afterwards I will look into assigning these out to
others who are interested and working on some myself as well.

Paul

On Apr 9, 2:55 am, Torsten <torstenzan...@googlemail.com> wrote:
> Hi Paul,
>
> My namei st Torsten Zander and I would like to help the project as far as
> I can.
> I am not familiar with the code but but starting with some small tasks
> I shouldn't be
> a problem getting inti it, since the code is well written.
>
> Torsten
>
> Torsten Zander
> Webentwicklung & Consulting
>

> Hildastr. 3                Email: i...@tzander.de
> 65189 Wiesbaden     Tel:   +49611-1747870
>
> 2009/4/6 Paul <apshoema...@gmail.com>:

[Paul]

Everyone,

As an update (maybe I'll start a new thread at some point, but this is
just clerical really), I wanted to let everyone know that I have
created a new branch in the repository called 2.0.3. If there are no
objections I would like to approach the release cycle thusly: the
trunk contains the latest stable code and we create branches for the
purpose of the next point release. This way, there will always be a
branch that represents the next phase of development while the trunk
is only to be committed against if there are hotfixes that need to be
pushed to production right away (in which case the source tarball can
be updated with the latest version of the trunk). When an official
point release has been scheduled to be released, I will merge the
changes into the trunk and we can package a tarball on the google code
site.

In reading through the svn logs, it seems that a 2.1.0 branch was
created but no code has been committed against it yet. I assume there
were plans for this branch that never reach fruition. At the moment
since the team is very small, I will be making much smaller strides in
releases. I'm not going to delete this branch at the moment because I
am sure we will work up to that and if the team gets large enough to
where we can devote resources to a much later phase of development we
can begin working on that sooner rather than later. I would also like
to mirror what seems to be the current approach when it comes to
experimental contributions that may disrupt the already established
architecture to xinc. If you have an idea that will require a
significant restructuring of the core architecture, please create a
separate branch (or I can do that, if you don't have permission) and
we will set you up to commit against that for testing purposes.

Also, I have worked through a lot the issues and tagged them
appropriately as feature, documentation, defect, etc. I will begin
working on defects today or tomorrow.

As an aside and a shameless plug, my amount of free time has greatly
increased as I just found out that the parent company (Ticketmaster)
that owns the company I work for (Echomusic) is shutting us down and
moving the operation to LA. This all due to our economic downturn
here in the states. If any of you have any leads on opportunities
that I may be a good fit for, please don't hesitate to email me. I
have a copy of my resume up on http://www.ideacandi.com. Ok, that'll
be the last I say of that ... time to get to work :-)

Paul

[Torsten]

hi everyone

in order to get to know the sources better a way to get all unitests
run at once, I can't see any Alltests files.

Thanks

2009/4/17 Paul <apsho...@gmail.com>:

--
Viele Grüße
Torsten

[Katrina]

Hi, I see that I'm late to the party.

I work as a professional developer in the Los Angeles area.

I am getting my team used to the idea of Continuous Integration, and
would love to contribute to the Xinc project.

Start me off small, please :)
I'd rather have some small successes and then ask for more, than leave
something hanging for ages!

Katrina

> have a copy of my resume up onhttp://www.ideacandi.com.  Ok, that'll