Hey Ricardo,
For this kind of process, I think that using hg-svn or git-svn would really aid your workflow a lot. Then you can easily keep in sync with the opencv stuff in SVN but still easily commit and maintain branches in your own private hg/git repo. That also means you can easily try out any changes you want and commit them locally.
I added you to the sourceforge project, welcome!
.hc
On Oct 17, 2011, at 3:29 PM, lluis gomez i bigorda wrote:
hi,
We (me and Yves) have talked a bit with ricardo off-list, for us is ok if ricardo have commit access to the pd_opencv externals.
But, ricardo, remember We prefer to discuss any changes of the existing code before commiting (specially if it's in the autotools build stuff) ... so, please let's continue using the patch tracker for this things ok? I promise to be more "effective" on this.
best, ll.
Al 17/10/11 20:18, En/na Hans-Christoph Steiner ha escrit:
Just have Lluis or Yves email pd-dev to ask commit access for you, and I'll add you.
.hc
On Oct 17, 2011, at 1:33 PM, Ricardo Fabbri wrote:
Hello, Hans,
Thanks for your remarks. I really think the patch tracker is a great and important tool, but what I was letting you know is that it is being inefficient in practice for my specific case with the specific developers of puredata_opencv.
Lluis & Yves both agreed that I could develop pix_opencv and pdp_opencv and actually asked me to keep working on the SVN repository. They gave me specific guidelines: adding stuff straight on is OK, but modifying existing stuff requires some discussion with them.
So acces to externals/pdp_opencv and externals/pix_opencv is a good place to start. I need a faster route to developing there as I am having to ship files around to friends & mailing lists that need my simple but important changes.
Regarding the remainder of the repository, there is no immediate necessity right now, but there will be soon.
Best regards,
---------- Forwarded message ---------- From: *lluis gomez i bigorda* <lluisgomez@hangar.org mailto:lluisgomez@hangar.org> Date: Thu, Sep 22, 2011 at 9:18 AM Subject: Re: pix_opencv, pdp_opencv To: "ydegoyon@gmail.com mailto:ydegoyon@gmail.com" <ydegoyon@gmail.com mailto:ydegoyon@gmail.com> Cc: Ricardo Fabbri <rfabbri@gmail.com mailto:rfabbri@gmail.com>
Hi Ricardo,
I have more or less the same "feeling" that Yves ... there's no need to work in a separate version control system ... or it is?
Also, as We don't know us personally and We still don't know the way We like to do things... I think it's a good idea to preserve a bit the original code of the libs, let's say there is an "informal" rule working with the code on pix_opencv, pdp_opencv, more or less it's like this :: There is no problem at all adding new objects or files if doesn't breaks nothing of the existing ones, but for modifying the previous code please discuss it first to commit ...
I hope you understand this ... think that pd_opencv has no stable version nor "official" snapshots, so the only way to get the code is via sourceforge and We want to mantain certain "stability" there ... this is specially important for the autotools system fo example ... now it works perfectly.
Well this is more or less what We are doing until now, We already had some contributions on that way... and it seems to work :)
For sure, With time things could change if We get more confidence ...
On the other hand, I must say I'm pleassed to have more people working together in pd_opencv. For sure there a millions of things to explore!
best, ll.
Ricardo
Linux registered user #175401 www.lems.brown.edu/~rfabbri http://www.lems.brown.edu/~rfabbri
On Mon, Oct 17, 2011 at 3:10 PM, Hans-Christoph Steiner <hans@at.or.at mailto:hans@at.or.at> wrote:
Hey Ricardo,
Its great that you are working on pix_opencv there. That library can do a lot and still has lots of potential, so more dev work there should produce fun stuff.
The patch tracker process may seem onerous, but I find that it is quite useful for discussing patches and changes. It is not at all meant to be a barrier to committing, instead it is a useful tool to handle different situations. Also, getting added to the sourceforge project does not mean you can start committing anywhere in the pure-data repository. For pix_opencv stuff, you will still need to go thru its authors before committing anything. It is up to the person wanting to commit to get explicit permission from the author/maintainer of that library before committing any changes. For example, IOhannes has asked everyone to go thru the patch/bug tracker for zexy changes, and though I have the technical permissions to commit to zexy, I post my changes to the tracker.
Lastly, I saw that you posted the patches to pix_opencv, but I don't know that code at all, so I can't really evaluate it. If you post a patch for code that I know, then I'll review it, and then have a place to judge from. If the pix_opencv authors say they want you to have commit access, then I'll add you. There are other administrators too that can grant access if they want to.
.hc
On Oct 16, 2011, at 8:07 PM, Ricardo Fabbri wrote:
Dear Hans, I've been writing patches to pix_opencv, a tiny one that was already incorporated, and the other which is more significant but is taking time from Lluis to be applied. I was going to wait until I sent you some larger patches,however, I wonder if I could get commit access already since the patch tracker scheme is taking unnecessary time from people (both from you and from users that take long to see the changes). Perhaps I could be in a watch period where I email you & the responsible externals person every single commit that I make.
Anyways, I am also perfectly OK with having to wait longer.I just would like you to know about the situation.
Sincerely, Ricardo -- Linux registered user #175401 www.lems.brown.edu/~rfabbri <http://www.lems.brown.edu/~rfabbriOn Sat, Oct 1, 2011 at 7:25 PM, Hans-Christoph Steiner <hans@at.or.at <mailto:hans@at.or.at>> wrote: That's a good idea, try looking in the bug tracker and starting there with any bug that you are interested in. .hc On Sat, 2011-10-01 at 19:18 -0300, Ricardo Fabbri wrote: Thank you, Hans. I think that sounds reasonable. The hard drive from the big computer I was working with just died, so I am having this transition time to deal with anyways. Soon enough I'll come up with the patches. If there is any bug specifically you'd like to see fixed, let me know and maybe I can give a shot at it. Best, On Saturday, October 1, 2011, Hans-Christoph Steiner <hans@at.or.at <mailto:hans@at.or.at>> wrote: Hey Ricardo, Welcome, its great to have you working on Pd!This Lab Macambira
sounds very promising. The way things work with getting SVN access is 'lazy consensus'. Basically we wait for a while and if no one objects, an admin will add you as a committer. Since you are new to contributing to Pd, I'd like to see a patch or two from youbefore adding you.
.hc On Wed, 2011-09-28 at 19:26 -0300, Ricardo Fabbri wrote: Hello, all, I would like to introduce myself and humbly request to be a Pd committer. Following http://puredata.info/docs/__developer/SVNCommitAccess <http://puredata.info/docs/developer/SVNCommitAccessthis is the required info: My name is Ricardo Fabbri and I have been working with free software since 1999, specializing in computer vision and image processing. During my PhD I worked on 3D reconstruction algorithms and video camera self-calibration, and have also worked for Google in applications of related technology for the scanning and indexing of books and other print material. I have recently returned to Brazil where I helped found the free software group Lab Macambira (labmacambira.sf.net <http://labmacambira.sf.net>), together with my brother Renato Fabbri, Vilson Vieira, and others. We are currently a team of 15. My brother had a significant influence in Pd Con that was held in Brazil, as well as in the rise of the Brazilian Pd and Linux community. My brother is a composer and is doing graduate work in computational physics. I was actually the one whointroduced him to Pd and Linux back in the days when he was working with Max. We were also joined
by Gilson Beck, another composer who got hooked on Pd. Currently, my direct interests with Pd development are to support the demands from these composers, but, mainly, to support Pdas a core component of
our real-time video processing stack. We use Pd for guiding C++ modules linked to OpenCV and VXL. We also use Scilab as a quick prototyping language for new algorithms. As you can see, Pd is the guiding master of our systems, so it is crucial for us to have a development grip on it. Commit access is important as we would like to develop thiskey component with you.
You can count on our painstaking care not tobreak anything and our willing service to improve Pd. Perhaps with a commit access it will make it easier to do small improvements and documentation, for a start, or bigger things such as adding completely new
functionality. Our concrete plans for developing Pd are related to pix_opencv: adding new functionality, providing bugfixes, and modifying pix_opencv_bgstats to allow for different background modeling algorithms, and also profiling it to make it faster and more responsive. We plan to help maintain puredata_opencv in general, as well as helping you guys out with whatever you need. We were also thinking about helping to migrate the community pd-svn repository to Git, or even Gem to Git, so that at least all our repos are under the sameversion control. Any suggestions on how to help are more than welcome. We are very
glad to be interacting with you. SF user: ricardofabbri. Optionally, Vilson's SF user: vilsonvieiraand My brother's:
greenkobold Best regards, Ricardo -- Linux registered user #175401 www.lems.brown.edu/~rfabbri <http://www.lems.brown.edu/~rfabbri>
Pd-dev mailing list Pd-dev@iem.at <mailto:Pd-dev@iem.at> http://lists.puredata.info/__listinfo/pd-dev <http://lists.puredata.info/listinfo/pd-dev> -- Ricardo -- Linux registered user #175401 www.lems.brown.edu/~rfabbri <http://www.lems.brown.edu/~rfabbri>------------------------------__------------------------------ __----------------
You can't steal a gift. Bird gave the world his music, and if you can hear it, you can have it. - Dizzy Gillespie
News is what people want to keep hidden and everything else is publicity. - Bill Moyers
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
----------------------------------------------------------------------------
Programs should be written for people to read, and only incidentally for machines to execute. - from Structure and Interpretation of Computer Programs