I found it easier to work with the Github repos myself. I've had a hard time 
locating all of the repos for the various components on the current Git server. 
Having it on Github would make it easy to have all of them stored under either 
an Adiscon or Rsyslog organization. Plus it allows forking within the system 
and makes submitting pull requests much simpler.

Also, I'm not personally against the idea of Rsyslog becoming an Apache 
project. I and I suspect David as well, was pointing out that there may be some 
solid business reasons not to do so. And Rainer has a good question about the 
licensing as well.

I think a solid list of potential benefits would be extremely helpful in 
convincing them that doing so is in the best interest of their company and the 
product.

-- James
-- Sent from my mobile --

----- Reply message -----
From: "Rainer Gerhards" <[email protected]>
To: "rsyslog-users" <[email protected]>
Subject: [rsyslog] Rsyslog => Apache?
Date: Thu, Dec 12, 2013 4:29 AM

Just a tiny note due to overload ;)

On Thu, Dec 12, 2013 at 11:05 AM, Radu Gheorghe <[email protected]>wrote:

> Hi,
>
> I'll leave it to Otis to give more details, because he's an Apache
> committer, but I believe there's a misunderstanding here.
>
> An Apache project can still be backed up by a commercial company. Lots of
> projects are, like Solr, Flume (another logging product!) and so on. The
> main advantage I see is that it's easier for the community to contribute
> and drive the project forward. It's a model that seems to work for
> open-source software, and lots of projects who got in there are doing very
> well - very active, growing, lots of people offering
> consulting&support&professional services, building more complex products on
> top of them, packaging them in various ways, etc
>
> I think this is an idea that would help drive more contributions and
> hopefully solve the 24 hours/day problem that keeps popping up lately, more
> and more as rsyslog gets more attention. To prove the "attention" theory,
> let's look at some trends for rsyslog and some other products that came up
> in discussions lately:
>
> http://www.google.com/trends/explore#q=rsyslog%2C%20logstash%2C%20syslog-ng&cmpt=q
>
> And the mailing list traffic:
> http://dir.gmane.org/gmane.comp.sysutils.rsyslog
>
> Maybe going to Apache would be a crazy idea in the sense that it requires
> following that procedure. And people already have too little time. Maybe a
> less crazy idea is just to put it on GitHub or somewhere similar where it
> would be easy to just send pull requests.


Well... done so 6 month ago ;) This is the initial blog post with some
progress:

http://blog.gerhards.net/2013/05/moving-to-github.html

Was announced at several places. Overall feedback is "not bad, but no real
difference".

Rainer


> This will not only make code
> patches easier, but I'm thinking at documentation, tests, issues, all in
> one place.
>
> Not only contributions would be easier, but it would make things would be
> more visible. Your github profile counts for many as some sort of CV. The
> more&better you contribute, the more awesome you are (think job
> opportunities and such). For the project, it would make it easier to see
> how it evolves: contributions, issues, wiki - again, all in one place. That
> is familiar to many.
>
> Apache takes this idea to a higher level, as far as I understand, so crazy
> could be crazy-good. *Could be* - I don't know, really, I'm lacking
> knowledge about how Adiscon and Apache works, although I have some idea
> about both. Otis, maybe you can say some more about the advantages (and
> disadvantages)?
>
> And I'm obviously curious about what the Adiscon guys have to say about
> this.
>
> Best regards,
> Radu
>
> 2013/12/11 Boylan, James <[email protected]>
>
> > I agree with David. As a business who developsand supports a product, I
> > can't see any reason for Adiscon to do so unless they decide to no longer
> > support and develop the software.
> >
> > -- James
> > -- Sent from my mobile --
> >
> > ----- Reply message -----
> > From: "David Lang" <[email protected]>
> > To: "rsyslog-users" <[email protected]>
> > Subject: [rsyslog] Rsyslog => Apache?
> > Date: Wed, Dec 11, 2013 3:09 PM
> >
> > not being an adiscon person, my first question is why they would want to
> do
> > that?
> >
> > David Lang
> >
> > On Wed, 11 Dec 2013, Otis Gospodnetic wrote:
> >
> > > Date: Wed, 11 Dec 2013 16:05:11 -0500
> > > From: Otis Gospodnetic <[email protected]>
> > > Reply-To: rsyslog-users <[email protected]>
> > > To: rsyslog-users <[email protected]>
> > > Subject: [rsyslog] Rsyslog => Apache?
> > >
> > > Hi,
> > >
> > > Maybe this is a completely crazy question, but has Adiscon ever
> > considered
> > > moving Rsyslog to Apache?
> > >
> > > Thanks,
> > > Otis
> > > --
> > > Performance Monitoring * Log Analytics * Search Analytics
> > > Solr & Elasticsearch Support * http://sematext.com/
> > > _______________________________________________
> > > rsyslog mailing list
> > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > http://www.rsyslog.com/professional-services/
> > > What's up with rsyslog? Follow https://twitter.com/rgerhards
> > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a
> myriad
> > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> > DON'T LIKE THAT.
> > >
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > http://www.rsyslog.com/professional-services/
> > What's up with rsyslog? Follow https://twitter.com/rgerhards
> > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> > DON'T LIKE THAT.
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > http://www.rsyslog.com/professional-services/
> > What's up with rsyslog? Follow https://twitter.com/rgerhards
> > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> > DON'T LIKE THAT.
> >
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> DON'T LIKE THAT.
>
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to