Does cacti have a cvs repository somewhere ?
or should any diffs/change suggestions just be submitted against 0.6.7?
CVS?
Moderators: Developers, Moderators
-
gwynnebaer
- Posts: 35
- Joined: Sat Apr 13, 2002 5:16 pm
- Location: Santa Barbara, CA
There have been a lot of requests for a CVS repository for cacti so far, so I will address my options and issues now so they can hopefully be resolved. I also want to ask questions to anyone else out there that has done this before and has some light to shed on the idea.
A CVS server would be a very useful thing for both me and users/developers of cacti. Users will be able to grab development copies of cacti, and developers will not have to send me patches for small bug fixes/feature additions. Here is my own gripe though (and maybe its just my lack of understanding for CVS) is the lack of developer control.
If anything, I would prefer to have some sort of control over what major features and what direction cacti decides to head in. Now, don't get me wrong... this kind of thing would be GREAT for anyone that wants to contribute to cacti, and this is a good thing in my mind. However, there is also a certain level of consistency that goes into the front-end of cacti that makes it much easier to learn/use. I think back-end wise, there is a lot that could be changed and done a lot better in my mind. This is where a CVS server would really shine.
I guess in addition to these comments, I also have a few general overall questions:
How do you dish out rights to the CVS tree? Who can checkout modules, who can update the tree?
What happens when someone decides to submit their "really cool patch" that isn't regarded as a very good move forward for cacti? Who has authority on the CVS tree, and more importantly who decides what goes into the official cacti distribution?
As for hosting, I think SourceForge would work unless someone else has a more flexible option. Please excuse my ignorance when it comes to CVS, I have little practical experience with it. I hope that anyone with relevant experience posts their thoughts/answers to the matter.
Thanks for all the cooperation!
-Ian
A CVS server would be a very useful thing for both me and users/developers of cacti. Users will be able to grab development copies of cacti, and developers will not have to send me patches for small bug fixes/feature additions. Here is my own gripe though (and maybe its just my lack of understanding for CVS) is the lack of developer control.
If anything, I would prefer to have some sort of control over what major features and what direction cacti decides to head in. Now, don't get me wrong... this kind of thing would be GREAT for anyone that wants to contribute to cacti, and this is a good thing in my mind. However, there is also a certain level of consistency that goes into the front-end of cacti that makes it much easier to learn/use. I think back-end wise, there is a lot that could be changed and done a lot better in my mind. This is where a CVS server would really shine.
I guess in addition to these comments, I also have a few general overall questions:
How do you dish out rights to the CVS tree? Who can checkout modules, who can update the tree?
What happens when someone decides to submit their "really cool patch" that isn't regarded as a very good move forward for cacti? Who has authority on the CVS tree, and more importantly who decides what goes into the official cacti distribution?
As for hosting, I think SourceForge would work unless someone else has a more flexible option. Please excuse my ignorance when it comes to CVS, I have little practical experience with it. I hope that anyone with relevant experience posts their thoughts/answers to the matter.
Thanks for all the cooperation!
-Ian
-
gwynnebaer
- Posts: 35
- Joined: Sat Apr 13, 2002 5:16 pm
- Location: Santa Barbara, CA
my suggestion from one who uses CVS on a daily basis is this:
1. open up the CVS tree read-only to anyone who wants it (obvious)
2. have people send you patches and updates the "hard way" via email until you start to get a feel for:
-gwynnebaer
1. open up the CVS tree read-only to anyone who wants it (obvious)
2. have people send you patches and updates the "hard way" via email until you start to get a feel for:
- i. that person's abilities and submissions
ii. your tolerance for allowing others to affect the code tree directly vs.
iii. your tolerance for applying patches manually the "hard way".
-gwynnebaer
CVS
Has there been any progress with the idea of running a CVS for cacti?
I for one would be very very pleased to see such a thing, as I have an itching need to work on this project...oh, no, wait, thats my boss tapping me on the shoulder, wanting me to get a new network monitoring solution in place!
Seriously, I would like to see further developments in cacti, and I believe I could help if I had the ability to see where current work is at. Obviously coherency is needed in the development, so it would be best to have the CVS tree read-only, but this is all that is needed for people like myself who would like to contribute to future developments (e.g. version 0.
to be able to do so.
I for one would be very very pleased to see such a thing, as I have an itching need to work on this project...oh, no, wait, thats my boss tapping me on the shoulder, wanting me to get a new network monitoring solution in place!
Seriously, I would like to see further developments in cacti, and I believe I could help if I had the ability to see where current work is at. Obviously coherency is needed in the development, so it would be best to have the CVS tree read-only, but this is all that is needed for people like myself who would like to contribute to future developments (e.g. version 0.
to be able to do so.Setting up a cvs
Hello all,
I am willing to set up a CVS system...but I have not set one up before...It should not be too hard....is everyone ok with using ssh to connect but SSH method does not provide a way for anonymous users to get the sources...so i might just stick with the CVS password server protocol...let me know...
I am willing to set up a CVS system...but I have not set one up before...It should not be too hard....is everyone ok with using ssh to connect but SSH method does not provide a way for anonymous users to get the sources...so i might just stick with the CVS password server protocol...let me know...
Hi Guys.
CVS is already set up at Cacti's SourceForge site. However, we're in the middle of a pretty massive overhaul so I'd urge you to wait a bit before submitting patches as they may no longer be useful in the final incarnation of this version. After the next release, we'll be in a much better position to accept patches and get them integrated.
And I'll warn you now - the stuff in CVS right now is mostly non-functional because we're making so many changes in the fundamentals of how Cacti works so it's prolly not even worth your time checking it out just yet. When we've got something we think is ready for Alpha, we'll let everybody know.
Thanks,
Rob.
CVS is already set up at Cacti's SourceForge site. However, we're in the middle of a pretty massive overhaul so I'd urge you to wait a bit before submitting patches as they may no longer be useful in the final incarnation of this version. After the next release, we'll be in a much better position to accept patches and get them integrated.
And I'll warn you now - the stuff in CVS right now is mostly non-functional because we're making so many changes in the fundamentals of how Cacti works so it's prolly not even worth your time checking it out just yet. When we've got something we think is ready for Alpha, we'll let everybody know.
Thanks,
Rob.
Who is online
Users browsing this forum: No registered users and 1 guest