[Monotone-devel] Introduction: Pablo
Hi Everyone, My name is Pablo I work as the Lead Developer and Systems Analyst at the Trust in Miami, FL. We are currently using Monotone for one of our internal projects and so far I must say I really like it. If it proves it self it well replace the cvs servers. This was after careful consideration and huge debates with the I.T Manager and others who were pushing for Mercurial or Git. I obviously won that battle LOL. During the evaluation process several factors were taken into consideration, how the code was written was also a determining factor for the choice. After looking at HG (python .. yuck) I knew that was one software I would not stick my nose in. Git, came close and had a few features that I like that monotone was missing. But overall monotone was simple to use, flexible, stable, secure and had the most hooks allowing for tight integration with other software used for Developement Tracking and work just as the documentation stated it should work. Great Job!!! So you are probably wonder what skills I have and how I would like to help the project (other wise stop posting junk email in our mailing list ), right. Well, I have experience programming in C++ (my prefered programming language) although I must admit its been about 3 or 4 years I don't work on a C or C++ application. Currently I have been stuck working with PHP and Java. I also, have experience in systems management of UNIX or Linux servers such as Solaris, FreeBSD, Linux: RedHat (Yuck I know I only did it for work, lol), Suse, Slackware and Debian. I have also worked and currently work as a development project manager were I had to design, document and implement a development life cycle, and release cycle. I hope that I can be of help. I was reading your ROADMAP file in the src directory and saw that you guys are looking to write up a HACKERS guide for coding monotone. Maybe I can look at the code as I study it and start writing up a draft. Also, does the team have a formal SDLC? If so were can I read up on it? Ok, that will be all for now, I will stop myself from rambling on, LOL!!! Regards, Pablo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Non-modal merge
Stefan Monnier [EMAIL PROTECTED] writes: Bak when I used monotone for the first time, I was surprised to see that all the merge options provided were pretty much modal. So I came up with the code attached below (not on my own, it's largely copied from random bits on the Web, it's probably hideous for Lua experts). Is there such a tool in standard now? Not in standard, but I put one in contrib/diff3_keep_conflicts_merger.lua The objection is that this allows conflicts to be commited to the database. In most situations, I don't have a problem with that, and I definitely prefer the non-modal behavior; often I don't have time to fix all the conflicts immediately. If you don't want the conflicts committed, you can use merge_into_workspace, although that has other problems. For one thing, it's undocumented :). For another, it leaves the workspace with two parents, which is not typical, and Emacs DVC can't handle it (yet). It would be nice if the top-level merger code output a summary of conflicts in this case, so it would be easier to keep a list of things to go back and fix, but the current output isn't too bad for that purpose. There was some discussion of having mtn keep track of the conflicts, but I think that's unnecessary. One difference between our scripts is that I ignore the return value, while you check for ret 1. I guess diff3 returns 1 for conflict, and 1 for error? The man page I have (in Cygwin) doesn't document the return value. Feel free to improve contrib/diff3_keep_conflicts_merger.lua -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Introduction: Pablo
Hi Pablo! Pablo Delgado schrieb: But overall monotone was simple to use, flexible, stable, secure and had the most hooks allowing for tight integration with other software used for Developement Tracking and work just as the documentation stated it should work. Great Job!!! Cool! Thanks! I hope that I can be of help. I was reading your ROADMAP file in the src directory and saw that you guys are looking to write up a HACKERS guide for coding monotone. Maybe I can look at the code as I study it and start writing up a draft. Also, does the team have a formal SDLC? If so were can I read up on it? AFAIK there is no such thing, we usually discuss something on the wiki [0], the IRC channel or on the mailing list, make an implementation in a branch (or send in a patch), write tests (unit tests and/or UI tests which are written in Lua), create documentation for the feature, put it for review and if it passes the review by a couple of people, we merge it into the main branch. From my experiences in the past this community usually returns the best results if a certain topic / feature is not discussed to death (bikeshed discussions usually produce nothing than hot air), but simply do a possible implementation, because code is in most cases way more formal than human language. And in general its better to start doing something which nags you with the current monotone, than doing just something, because in the latter case people are usually not motivated enough to complete it or do it good enough. Anyways, we're always happy to accept patches! Thomas. [0] http://www.venge.net/mtn-wiki/ [1] irc://irc.oftc.net/#monotone -- only dead fish swim with the stream: http://thomaskeller.biz/blog Am Anfang war das Wort: http://www.schäuble-muss-weg.de signature.asc Description: OpenPGP digital signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Introduction: Pablo
Pablo Delgado wrote: I hope that I can be of help. I was reading your ROADMAP file in the src directory and saw that you guys are looking to write up a HACKERS guide There is a HACKING file in the source directory as well. Cheers, Derek ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Monotone Commit Template
Hi Everyone, [name] recommended that I started working on something that I feel bothers me or I need. Well, one of this things is the commit templating capability that cvs has. This feature allows the repository manager to establish the basic structure of the commit message. This helps obvioudly review the log information so that it is not just a long list of changes. Example: PR: Submitted By: Reviewed By: Approved By: Description: MTN: -- MTN: Please fill out this commit message. MTN: MTN: PR: MTN: Enter a description of this change. MTN: Lines beginning with `MTN:' are removed automatically. MTN: MTN: Current branch: head MTN: Changes against parent 7d72b4f63082eab237b029d0ff1980f0be374f7a MTN: patched main.cpp MTN: -- MTN: ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Monotone Commit Template
This message was submitted incomplete to the accidently pressing enter on this keyboard. Here is the email as it was inteded to go out. -- Email Hi Everyone, Someone recommended that I started working on something that I feel bothers me or I need. Well, one of thing I miss is the commit templating capability that cvs has. This feature allows the repository manager or project leader to establish the basic structure of the commit message that they wish to use for their project. This helps obvioudly review the log information so that it is not just a long list of changes. Instead it provides additional useful information, and it would provide a way to create templates that would allow for easy parsing, for integrating with other systems. Example: PR Number: Submitted By: Reviewed By: Approved By: Description: MTN: -- MTN: Please fill out this commit message. MTN: MTN: Enter a description of this change. MTN: Lines beginning with `MTN:' are removed automatically. MTN: MTN: Current branch: head MTN: Changes against parent 7d72b4f63082eab237b029d0ff1980f0be374f7a MTN: patched main.cpp MTN: -- 1) What does everyone think of this idea? 2) Should a template file be stored in _MTN maybe call template? 3) Should the template be stored in the DB, so that all developers that work on a specific project gets the wanted template when performing a commit? Regards, Pablo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Monotone Commit Template
On Sat, 2007-09-22 at 22:25 -0600, Pablo Delgado wrote: Someone recommended that I started working on something that I feel bothers me or I need. Well, one of thing I miss is the commit templating capability that cvs has. This feature allows the repository manager or project leader to establish the basic structure of the commit message that they wish to use for their project. 1) What does everyone think of this idea? Yes. I'm surprised we don't have this yet, I know it was discussed before and I don't recall any objections. 2) Should a template file be stored in _MTN maybe call template? 3) Should the template be stored in the DB, so that all developers that work on a specific project gets the wanted template when performing a commit? It should probably be in the project root like .mtn-ignore is. -- Timothy Free (experimental) public monotone hosting: http://mtn-host.prjek.net ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
