From: Rob V. <rv...@do...> - 2016-04-11 10:11:18
|
Folks, So you may have noticed that there has not been any releases in a long time, and again you may have not since there is little to no activity here at all. Personally I no longer have the drive, time nor the capability (due to unforeseen health issues) to continue making any efforts to take this project forward or even to continue to maintain it. Therefore since no one else is helping out with this the project is for all intents and purposes dead. As a good friend in the open source community is fond of saying: There are three ways to participate in open source -hope, sponsor, contribute Unfortunately this project has never succeeded in building a community of contributors and has mostly relied on hoping someone else will do the work for them. I acknowledge that this is as much my failure to build a viable community as it is a failure of the community to get more heavily involved but unfortunately it leaves us in a situation where my stepping down essentially kills the project. Sorry to be leaving like this, Rob |
From: Khalil A. <ka...@ne...> - 2016-04-11 11:09:34
|
Hey Rob, I'm sorry to see you go, and more sorry that I haven't be contributing as much as I would have liked to / should have. However, I do fully understand your position - I've been in the same place myself with my open-source projects. I would like the awesome stuff that you have done with DNR to live on in some form. From a my perspective I will at the very least work on a fork of DNR as my company has a bunch of tools and services built on the libraries. However, if others are also willing to step up I'd be happy to talk about carrying the project as an open-source effort. If anyone else on this list would like to discuss if/how the project proceeds, speak up now guys! Cheers Kal On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse <rv...@do...> wrote: > Folks, > > So you may have noticed that there has not been any releases in a long > time, and again you may have not since there is little to no activity here > at all. > > Personally I no longer have the drive, time nor the capability (due to > unforeseen health issues) to continue making any efforts to take this > project forward or even to continue to maintain it. Therefore since no one > else is helping out with this the project is for all intents and purposes > dead. > > As a good friend in the open source community is fond of saying: > > There are three ways to participate in open source -hope, sponsor, > contribute > > Unfortunately this project has never succeeded in building a community of > contributors and has mostly relied on hoping someone else will do the work > for them. I acknowledge that this is as much my failure to build a viable > community as it is a failure of the community to get more heavily involved > but unfortunately it leaves us in a situation where my stepping down > essentially kills the project. > > Sorry to be leaving like this, > > Rob > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com |
From: Max - M. <ma...@mi...> - 2016-04-11 12:45:31
|
Hi Rob, All like Kal said, I'm also sorry to see you go. I wish I could have contributed more on the project last year, but the company I work for decided to switch to more mainstream technologies despite my efforts to make RDF our underlying standard (thus the long silence since my last PR). DNR is such an awesome library and I can't but admire the work and efforts you've invested into it since its creation. Thank you thousands of times for that. As for Kal's request, of course I feel DNR should continue since it is the only mature enough available RDF library for the .Net environment and I would hate to see it become yet another RDF project to go into oblivion and as much as I do not despair to get back to the semantic side, I do not unfortunately currently have the time neither the skills and Rob-wise preciseness to actively work on it. Anyway, I'd still like to contribute as much as I possibly can so count me in for any discussion about the project's future, Cheers and take care, Max. 2016-04-11 12:38 GMT+02:00 Khalil Ahmed <ka...@ne...>: > Hey Rob, > > I'm sorry to see you go, and more sorry that I haven't be contributing as > much as I would have liked to / should have. However, I do fully > understand your position - I've been in the same place myself with my > open-source projects. I would like the awesome stuff that you have done > with DNR to live on in some form. From a my perspective I will at the very > least work on a fork of DNR as my company has a bunch of tools and services > built on the libraries. However, if others are also willing to step up I'd > be happy to talk about carrying the project as an open-source effort. > > If anyone else on this list would like to discuss if/how the project > proceeds, speak up now guys! > > Cheers > > Kal > > On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse <rv...@do...> wrote: > >> Folks, >> >> So you may have noticed that there has not been any releases in a long >> time, and again you may have not since there is little to no activity here >> at all. >> >> Personally I no longer have the drive, time nor the capability (due to >> unforeseen health issues) to continue making any efforts to take this >> project forward or even to continue to maintain it. Therefore since no one >> else is helping out with this the project is for all intents and purposes >> dead. >> >> As a good friend in the open source community is fond of saying: >> >> There are three ways to participate in open source -hope, sponsor, >> contribute >> >> Unfortunately this project has never succeeded in building a community of >> contributors and has mostly relied on hoping someone else will do the work >> for them. I acknowledge that this is as much my failure to build a viable >> community as it is a failure of the community to get more heavily involved >> but unfortunately it leaves us in a situation where my stepping down >> essentially kills the project. >> >> Sorry to be leaving like this, >> >> Rob >> >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with Applications >> Manager >> Applications Manager provides deep performance insights into multiple >> tiers of >> your business applications. It resolves application problems quickly and >> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ >> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 >> <http://pubads.g.doubleclick.net/gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532> >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > <http://pubads.g.doubleclick.net/gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532> > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > |
From: Rob V. <rv...@do...> - 2016-04-12 09:16:20
|
Kal Don't forget that you have commit privileges so you can of course continue to maintain the official repository yourself if you wish. Also I can give you or anyone else who wants it write access to the dotnetrdf.org website, issue tracker etc. Rob From: Kal Ahmed <ka...@ne...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Monday, 11 April 2016 11:38 To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: Re: [dotNetRDF-Develop] End of line Hey Rob, I'm sorry to see you go, and more sorry that I haven't be contributing as much as I would have liked to / should have. However, I do fully understand your position - I've been in the same place myself with my open-source projects. I would like the awesome stuff that you have done with DNR to live on in some form. From a my perspective I will at the very least work on a fork of DNR as my company has a bunch of tools and services built on the libraries. However, if others are also willing to step up I'd be happy to talk about carrying the project as an open-source effort. If anyone else on this list would like to discuss if/how the project proceeds, speak up now guys! Cheers Kal On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse <rv...@do...> wrote: Folks, So you may have noticed that there has not been any releases in a long time, and again you may have not since there is little to no activity here at all. Personally I no longer have the drive, time nor the capability (due to unforeseen health issues) to continue making any efforts to take this project forward or even to continue to maintain it. Therefore since no one else is helping out with this the project is for all intents and purposes dead. As a good friend in the open source community is fond of saying: There are three ways to participate in open source -hope, sponsor, contribute Unfortunately this project has never succeeded in building a community of contributors and has mostly relied on hoping someone else will do the work for them. I acknowledge that this is as much my failure to build a viable community as it is a failure of the community to get more heavily involved but unfortunately it leaves us in a situation where my stepping down essentially kills the project. Sorry to be leaving like this, Rob ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532_______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
From: Khalil A. <ka...@ne...> - 2016-04-12 09:57:33
|
Hi Rob, I'm happy to continue working on DNR in the open - though if I am the only one who is going to spend time working on it I may change things up to suit my own development processes a bit as I'm more a Git/GitHub kinda guy. It would be great to keep the DNR domain and website. If I'm the only one working on things then I would prefer the issue tracker move over to GitHub with the repo to simplify / streamline things a bit. Ideally though I would prefer to do that sort of thing with some sort of community approval, and of course if there are a bunch of people who are happier with the current way things work then I'm also happy to talk about that too. So I'm going to put it out there as a proposal: 1) I'm willing to take over maintenance / development on DNR. I'm in a similar position to what Rob had recently - this won't be my full time work, it will have to fit in around stuff that actually pays the bills. However, as I said before we use DNR in commercial applications and in BrightstarDB so I at least have a some incentives to make sure stuff works ;-) 2) For my own ease of work I would like to transfer the DNR repo over to GitHub - this includes the issue tracker and, over time the wiki and possibly eventually the website too (the source code and issues would be the priority though). I would create a DotNetRDF Organization on GH that any other contributors would be free to join so the repos would be under something like github.com/DotNetRDF/.... 3) The project would keep the current MIT license. 4) I'm not in a position to actively maintain all of the different store integrations though (its quite a big ask to be constantly testing all of the different stores especially as some of them change quite frequently and require that weird-ass Java stuff ;-). I would be looking for volunteers to work on those and would probably split each one out into its own sub-project that can release at its own cadence. If anyone has any comments or opposition to that please raise it here. This is just a proposal and I won't be offended if people are against it or have other better ideas to put forwards! Rob, a couple of admin / ownership issues would arise here - these don't need to be actioned right now, I would just like to get an idea of what needs to happen if no one objects to the proposals above: a) Managing the dotnetrdf.org domain - I'm happy to take over the cost of maintaining the domain and any hosting that you are paying for. Or if you would prefer to keep the domain that is cool too. b) NuGet releases - I think this should be as simple as you adding a new package owner so that we can keep the existing NuGet package names. c) VDS.Common - as this is one of the key dependencies for DNR it would be good to know what your plans are with that project. Is it also something that should be transferred over ? d) Less important but currently the assemblies are signed right? It might be good to transfer the existing private key, but again its not a big deal if you would prefer to keep that and I just create a new private key for the next DNR release. Cheers Kal On Tue, Apr 12, 2016 at 9:58 AM, Rob Vesse <rv...@do...> wrote: > Kal > > Don't forget that you have commit privileges so you can of course continue > to maintain the official repository yourself if you wish. Also I can give > you or anyone else who wants it write access to the dotnetrdf.org > website, issue tracker etc. > > > Rob > > From: Kal Ahmed <ka...@ne...> > Reply-To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Date: Monday, 11 April 2016 11:38 > To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Subject: Re: [dotNetRDF-Develop] End of line > > Hey Rob, > > I'm sorry to see you go, and more sorry that I haven't be contributing as > much as I would have liked to / should have. However, I do fully > understand your position - I've been in the same place myself with my > open-source projects. I would like the awesome stuff that you have done > with DNR to live on in some form. From a my perspective I will at the very > least work on a fork of DNR as my company has a bunch of tools and services > built on the libraries. However, if others are also willing to step up I'd > be happy to talk about carrying the project as an open-source effort. > > If anyone else on this list would like to discuss if/how the project > proceeds, speak up now guys! > > Cheers > > Kal > > On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse <rv...@do...> wrote: > >> Folks, >> >> So you may have noticed that there has not been any releases in a long >> time, and again you may have not since there is little to no activity here >> at all. >> >> Personally I no longer have the drive, time nor the capability (due to >> unforeseen health issues) to continue making any efforts to take this >> project forward or even to continue to maintain it. Therefore since no one >> else is helping out with this the project is for all intents and purposes >> dead. >> >> As a good friend in the open source community is fond of saying: >> >> There are three ways to participate in open source -hope, sponsor, >> contribute >> >> Unfortunately this project has never succeeded in building a community of >> contributors and has mostly relied on hoping someone else will do the work >> for them. I acknowledge that this is as much my failure to build a viable >> community as it is a failure of the community to get more heavily involved >> but unfortunately it leaves us in a situation where my stepping down >> essentially kills the project. >> >> Sorry to be leaving like this, >> >> Rob >> >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with Applications >> Manager >> Applications Manager provides deep performance insights into multiple >> tiers of >> your business applications. It resolves application problems quickly and >> reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ >> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 >> <http://pubads.g.doubleclick.net/gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532> >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager Applications Manager provides deep performance insights into > multiple tiers of your business applications. It resolves application > problems quickly and reduces your MTTR. Get your free trial! > http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532_______________________________________________ > dotNetRDF-develop mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com |
From: Tomasz P. <tom...@gm...> - 2016-04-12 18:55:52
|
Hi guys, Rob, I'm very sorry to hear that you have to leave DotNetRDF. There is very unfortunate mix of slow adoption of RDF in general and poor community around it. This is especially true in the .NET space which resists any non-mainstream (and to some extent non-MS) stuff really. Sadly, this applies to many failed or marginalized .NET OSS projects. I am likely the least active of the contributors. Unfortunately I've only briefly used DNR at work and otherwise it is just side projects and ongoing personal interest, however we all know how that goes :(. Anyways, I've had little problems with the library lately. It mostly "just works" for whatever I needed it for. That said there is the 1.9 branch, which I've noticed has some prerelease packages released and the modularity is a good direction. If we need to choose I think we should invest in that. The current solution even proved troublesome to build locally sometimes for me. Also, it is simply a very complex project and I honestly feel daunted by the inner workings in some parts. Both would be a barrier for newcomers. More inline. Regards, Tom On 2016-04-12 11:57, Khalil Ahmed wrote: > Hi Rob, > > I'm happy to continue working on DNR in the open - though if I am the > only one who is going to spend time working on it I may change things > up to suit my own development processes a bit as I'm more a Git/GitHub > kinda guy. It would be great to keep the DNR domain and website. If > I'm the only one working on things then I would prefer the issue > tracker move over to GitHub with the repo to simplify / streamline > things a bit. Ideally though I would prefer to do that sort of thing > with some sort of community approval, and of course if there are a > bunch of people who are happier with the current way things work then > I'm also happy to talk about that too. > > So I'm going to put it out there as a proposal: > > 1) I'm willing to take over maintenance / development on DNR. I'm in a > similar position to what Rob had recently - this won't be my full time > work, it will have to fit in around stuff that actually pays the > bills. However, as I said before we use DNR in commercial applications > and in BrightstarDB so I at least have a some incentives to make sure > stuff works ;-) > > 2) For my own ease of work I would like to transfer the DNR repo over > to GitHub - this includes the issue tracker and, over time the wiki > and possibly eventually the website too (the source code and issues > would be the priority though). I would create a DotNetRDF Organization > on GH that any other contributors would be free to join so the repos > would be under something like github.com/DotNetRDF/.. > <http://github.com/DotNetRDF/..>.. I definitely support that. I proposed the move to Bitbucket but ever since I've moved to git and GitHub has only strengthened it's lead position in open source community through ease of contributing, rich features and 3rd party integrations. I think we should go that route, with easier solution and CI setup. First things first though. Alas, as I said, I am not and likely won't become a very active contributor but the least I could do is help with rebooting DNR at GitHub. Be it through solution and CI overhaul or moving wiki/issues/website to the new location. > > 3) The project would keep the current MIT license. > > 4) I'm not in a position to actively maintain all of the different > store integrations though (its quite a big ask to be constantly > testing all of the different stores especially as some of them change > quite frequently and require that weird-ass Java stuff ;-). I would be > looking for volunteers to work on those and would probably split each > one out into its own sub-project that can release at its own cadence. > > > If anyone has any comments or opposition to that please raise it here. > This is just a proposal and I won't be offended if people are against > it or have other better ideas to put forwards! > > Rob, a couple of admin / ownership issues would arise here - these > don't need to be actioned right now, I would just like to get an idea > of what needs to happen if no one objects to the proposals above: > > a) Managing the dotnetrdf.org <http://dotnetrdf.org> domain - I'm > happy to take over the cost of maintaining the domain and any hosting > that you are paying for. Or if you would prefer to keep the domain > that is cool too. > b) NuGet releases - I think this should be as simple as you adding a > new package owner so that we can keep the existing NuGet package names. > c) VDS.Common - as this is one of the key dependencies for DNR it > would be good to know what your plans are with that project. Is it > also something that should be transferred over ? > d) Less important but currently the assemblies are signed right? It > might be good to transfer the existing private key, but again its not > a big deal if you would prefer to keep that and I just create a new > private key for the next DNR release. > > Cheers > > Kal > > On Tue, Apr 12, 2016 at 9:58 AM, Rob Vesse <rv...@do... > <mailto:rv...@do...>> wrote: > > Kal > > Don't forget that you have commit privileges so you can of course > continue to maintain the official repository yourself if you wish. > Also I can give you or anyone else who wants it write access to > the dotnetrdf.org <http://dotnetrdf.org> website, issue tracker etc. > > > Rob > > From: Kal Ahmed <ka...@ne... > <mailto:ka...@ne...>> > Reply-To: dotNetRDF Developer Discussion and Feature Request > <dot...@li... > <mailto:dot...@li...>> > Date: Monday, 11 April 2016 11:38 > To: dotNetRDF Developer Discussion and Feature Request > <dot...@li... > <mailto:dot...@li...>> > Subject: Re: [dotNetRDF-Develop] End of line > > Hey Rob, > > I'm sorry to see you go, and more sorry that I haven't be > contributing as much as I would have liked to / should have. > However, I do fully understand your position - I've been in > the same place myself with my open-source projects. I would > like the awesome stuff that you have done with DNR to live on > in some form. From a my perspective I will at the very least > work on a fork of DNR as my company has a bunch of tools and > services built on the libraries. However, if others are also > willing to step up I'd be happy to talk about carrying the > project as an open-source effort. > > If anyone else on this list would like to discuss if/how the > project proceeds, speak up now guys! > > Cheers > > Kal > > On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse > <rv...@do... <mailto:rv...@do...>> wrote: > > Folks, > > So you may have noticed that there has not been any > releases in a long time, and again you may have not since > there is little to no activity here at all. > > Personally I no longer have the drive, time nor the > capability (due to unforeseen health issues) to continue > making any efforts to take this project forward or even to > continue to maintain it. Therefore since no one else is > helping out with this the project is for all intents and > purposes dead. > > As a good friend in the open source community is fond of > saying: > > There are three ways to participate in open source -hope, > sponsor, contribute > > Unfortunately this project has never succeeded in building > a community of contributors and has mostly relied on > hoping someone else will do the work for them. I > acknowledge that this is as much my failure to build a > viable community as it is a failure of the community to > get more heavily involved but unfortunately it leaves us > in a situation where my stepping down essentially kills > the project. > > Sorry to be leaving like this, > > Rob > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with > Applications Manager > Applications Manager provides deep performance insights > into multiple tiers of > your business applications. It resolves application > problems quickly and > reduces your MTTR. Get your free trial! > http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > <http://pubads.g.doubleclick.net/gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532> > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > <mailto:dot...@li...> > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > <mailto:kal...@ne...> > w: www.networkedplanet.com <http://www.networkedplanet.com> > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with > Applications Manager Applications Manager provides deep > performance insights into multiple tiers of your business > applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532_______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > <mailto:dot...@li...> > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with > Applications Manager > Applications Manager provides deep performance insights into > multiple tiers of > your business applications. It resolves application problems > quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > <mailto:dot...@li...> > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... <mailto:kal...@ne...> > w: www.networkedplanet.com <http://www.networkedplanet.com> > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
From: Khalil A. <ka...@ne...> - 2016-04-13 14:10:34
|
Yep I agree that the restructuring that is on the 1.9 branch would be a good place to start. The way I think I would tackle this would be to start with a full port of the hg repo to GitHub in its current state and then start on the restructuring so that we keep all the commit history. I'd appreciate the help on getting the CI stuff in place and maybe a walkthrough on how it all works with TeamCity so that I can also help to keep it running - we just moved over to TeamCity on-premise at work so I've at least got a bit of an idea what the different buttons do now! But what would be most useful right now would be to look at the project structure both the current one and the 1.9 branch and maybe collaborate on this list on coming up with a good way to move forward. At this point we could also talk about the build tools and the build process in general and see how we can simplify things. I'm hoping to get some time on Friday to have a deeper dive into this and see what ideas I can come up with...at that point I'll start a separate thread with my thoughts! Cheers Kal On Tue, Apr 12, 2016 at 7:55 PM, Tomasz Pluskiewicz < tom...@gm...> wrote: > Hi guys, > > Rob, I'm very sorry to hear that you have to leave DotNetRDF. There is > very unfortunate mix of slow adoption of RDF in general and poor > community around it. This is especially true in the .NET space which > resists any non-mainstream (and to some extent non-MS) stuff really. > Sadly, this applies to many failed or marginalized .NET OSS projects. > > I am likely the least active of the contributors. Unfortunately I've > only briefly used DNR at work and otherwise it is just side projects and > ongoing personal interest, however we all know how that goes :(. > Anyways, I've had little problems with the library lately. It mostly > "just works" for whatever I needed it for. > > That said there is the 1.9 branch, which I've noticed has some > prerelease packages released and the modularity is a good direction. If > we need to choose I think we should invest in that. The current solution > even proved troublesome to build locally sometimes for me. Also, it is > simply a very complex project and I honestly feel daunted by the inner > workings in some parts. Both would be a barrier for newcomers. > > More inline. > > Regards, > Tom > > On 2016-04-12 11:57, Khalil Ahmed wrote: > > Hi Rob, > > > > I'm happy to continue working on DNR in the open - though if I am the > > only one who is going to spend time working on it I may change things > > up to suit my own development processes a bit as I'm more a Git/GitHub > > kinda guy. It would be great to keep the DNR domain and website. If > > I'm the only one working on things then I would prefer the issue > > tracker move over to GitHub with the repo to simplify / streamline > > things a bit. Ideally though I would prefer to do that sort of thing > > with some sort of community approval, and of course if there are a > > bunch of people who are happier with the current way things work then > > I'm also happy to talk about that too. > > > > So I'm going to put it out there as a proposal: > > > > 1) I'm willing to take over maintenance / development on DNR. I'm in a > > similar position to what Rob had recently - this won't be my full time > > work, it will have to fit in around stuff that actually pays the > > bills. However, as I said before we use DNR in commercial applications > > and in BrightstarDB so I at least have a some incentives to make sure > > stuff works ;-) > > > > 2) For my own ease of work I would like to transfer the DNR repo over > > to GitHub - this includes the issue tracker and, over time the wiki > > and possibly eventually the website too (the source code and issues > > would be the priority though). I would create a DotNetRDF Organization > > on GH that any other contributors would be free to join so the repos > > would be under something like github.com/DotNetRDF/.. > > <http://github.com/DotNetRDF/..>.. > > I definitely support that. I proposed the move to Bitbucket but ever > since I've moved to git and GitHub has only strengthened it's lead > position in open source community through ease of contributing, rich > features and 3rd party integrations. I think we should go that route, > with easier solution and CI setup. > > First things first though. Alas, as I said, I am not and likely won't > become a very active contributor but the least I could do is help with > rebooting DNR at GitHub. Be it through solution and CI overhaul or > moving wiki/issues/website to the new location. > > > > > 3) The project would keep the current MIT license. > > > > 4) I'm not in a position to actively maintain all of the different > > store integrations though (its quite a big ask to be constantly > > testing all of the different stores especially as some of them change > > quite frequently and require that weird-ass Java stuff ;-). I would be > > looking for volunteers to work on those and would probably split each > > one out into its own sub-project that can release at its own cadence. > > > > > > If anyone has any comments or opposition to that please raise it here. > > This is just a proposal and I won't be offended if people are against > > it or have other better ideas to put forwards! > > > > Rob, a couple of admin / ownership issues would arise here - these > > don't need to be actioned right now, I would just like to get an idea > > of what needs to happen if no one objects to the proposals above: > > > > a) Managing the dotnetrdf.org <http://dotnetrdf.org> domain - I'm > > happy to take over the cost of maintaining the domain and any hosting > > that you are paying for. Or if you would prefer to keep the domain > > that is cool too. > > b) NuGet releases - I think this should be as simple as you adding a > > new package owner so that we can keep the existing NuGet package names. > > c) VDS.Common - as this is one of the key dependencies for DNR it > > would be good to know what your plans are with that project. Is it > > also something that should be transferred over ? > > d) Less important but currently the assemblies are signed right? It > > might be good to transfer the existing private key, but again its not > > a big deal if you would prefer to keep that and I just create a new > > private key for the next DNR release. > > > > Cheers > > > > Kal > > > > On Tue, Apr 12, 2016 at 9:58 AM, Rob Vesse <rv...@do... > > <mailto:rv...@do...>> wrote: > > > > Kal > > > > Don't forget that you have commit privileges so you can of course > > continue to maintain the official repository yourself if you wish. > > Also I can give you or anyone else who wants it write access to > > the dotnetrdf.org <http://dotnetrdf.org> website, issue tracker etc. > > > > > > Rob > > > > From: Kal Ahmed <ka...@ne... > > <mailto:ka...@ne...>> > > Reply-To: dotNetRDF Developer Discussion and Feature Request > > <dot...@li... > > <mailto:dot...@li...>> > > Date: Monday, 11 April 2016 11:38 > > To: dotNetRDF Developer Discussion and Feature Request > > <dot...@li... > > <mailto:dot...@li...>> > > Subject: Re: [dotNetRDF-Develop] End of line > > > > Hey Rob, > > > > I'm sorry to see you go, and more sorry that I haven't be > > contributing as much as I would have liked to / should have. > > However, I do fully understand your position - I've been in > > the same place myself with my open-source projects. I would > > like the awesome stuff that you have done with DNR to live on > > in some form. From a my perspective I will at the very least > > work on a fork of DNR as my company has a bunch of tools and > > services built on the libraries. However, if others are also > > willing to step up I'd be happy to talk about carrying the > > project as an open-source effort. > > > > If anyone else on this list would like to discuss if/how the > > project proceeds, speak up now guys! > > > > Cheers > > > > Kal > > > > On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse > > <rv...@do... <mailto:rv...@do...>> wrote: > > > > Folks, > > > > So you may have noticed that there has not been any > > releases in a long time, and again you may have not since > > there is little to no activity here at all. > > > > Personally I no longer have the drive, time nor the > > capability (due to unforeseen health issues) to continue > > making any efforts to take this project forward or even to > > continue to maintain it. Therefore since no one else is > > helping out with this the project is for all intents and > > purposes dead. > > > > As a good friend in the open source community is fond of > > saying: > > > > There are three ways to participate in open source -hope, > > sponsor, contribute > > > > Unfortunately this project has never succeeded in building > > a community of contributors and has mostly relied on > > hoping someone else will do the work for them. I > > acknowledge that this is as much my failure to build a > > viable community as it is a failure of the community to > > get more heavily involved but unfortunately it leaves us > > in a situation where my stepping down essentially kills > > the project. > > > > Sorry to be leaving like this, > > > > Rob > > > > > ------------------------------------------------------------------------------ > > Find and fix application performance issues faster with > > Applications Manager > > Applications Manager provides deep performance insights > > into multiple tiers of > > your business applications. It resolves application > > problems quickly and > > reduces your MTTR. Get your free trial! > > http://pubads.g.doubleclick.net/ > > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > > < > http://pubads.g.doubleclick.net/gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > > > > _______________________________________________ > > dotNetRDF-develop mailing list > > dot...@li... > > <mailto:dot...@li...> > > > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > > > > > -- > > Kal Ahmed > > Director, Networked Planet Limited > > e: kal...@ne... > > <mailto:kal...@ne...> > > w: www.networkedplanet.com <http://www.networkedplanet.com> > > > ------------------------------------------------------------------------------ > > Find and fix application performance issues faster with > > Applications Manager Applications Manager provides deep > > performance insights into multiple tiers of your business > > applications. It resolves application problems quickly and > > reduces your MTTR. Get your free trial! > > http://pubads.g.doubleclick.net/ > > > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532_______________________________________________ > > dotNetRDF-develop mailing list > > dot...@li... > > <mailto:dot...@li...> > > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > > ------------------------------------------------------------------------------ > > Find and fix application performance issues faster with > > Applications Manager > > Applications Manager provides deep performance insights into > > multiple tiers of > > your business applications. It resolves application problems > > quickly and > > reduces your MTTR. Get your free trial! > > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > _______________________________________________ > > dotNetRDF-develop mailing list > > dot...@li... > > <mailto:dot...@li...> > > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > > > > > -- > > Kal Ahmed > > Director, Networked Planet Limited > > e: kal...@ne... <mailto:kal...@ne...> > > w: www.networkedplanet.com <http://www.networkedplanet.com> > > > > > > > ------------------------------------------------------------------------------ > > Find and fix application performance issues faster with Applications > Manager > > Applications Manager provides deep performance insights into multiple > tiers of > > your business applications. It resolves application problems quickly and > > reduces your MTTR. Get your free trial! > > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > > > > > _______________________________________________ > > dotNetRDF-develop mailing list > > dot...@li... > > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com |
From: Rob V. <rv...@do...> - 2016-05-19 09:51:26
|
Comments inline: On 12/04/2016 19:55, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi guys, > >Rob, I'm very sorry to hear that you have to leave DotNetRDF. There is >very unfortunate mix of slow adoption of RDF in general and poor >community around it. This is especially true in the .NET space which >resists any non-mainstream (and to some extent non-MS) stuff really. >Sadly, this applies to many failed or marginalized .NET OSS projects. > >I am likely the least active of the contributors. Unfortunately I've >only briefly used DNR at work and otherwise it is just side projects and >ongoing personal interest, however we all know how that goes :(. >Anyways, I've had little problems with the library lately. It mostly >"just works" for whatever I needed it for. > >That said there is the 1.9 branch, which I've noticed has some >prerelease packages released and the modularity is a good direction. If >we need to choose I think we should invest in that. The current solution >even proved troublesome to build locally sometimes for me. Also, it is >simply a very complex project and I honestly feel daunted by the inner >workings in some parts. Both would be a barrier for newcomers. Part of the issue is that the 1.9 Branch is not just a division into small modules but very much a ground up rewrite and as such I ran out of steam because it is a daunting task. The very core i.e. Nodes, triples, quads, graphs and collections thereof is complete and fairly stable though with some fairly major Breaking changes. The basic IO API was also pretty much done though some of the dynamic loading I/O formats was not working correctly. I had started on writing a completely new query engine but that was nowhere near complete and a lot of important supporting pieces such as a query parser are notably missing. https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Architecture/Design/2.0 details what I was heading towards that is by no means accurate reflection of What I actually implemented once I started making changes For any project of this size large-scale changes are slow, painful and boring to implement which makes it hard to attract people to do the work. It is often easier to continue to maintain a bloated and somewhat broken implementation than it is to do a new one. Rob > >More inline. > >Regards, >Tom > >On 2016-04-12 11:57, Khalil Ahmed wrote: >> Hi Rob, >> >> I'm happy to continue working on DNR in the open - though if I am the >> only one who is going to spend time working on it I may change things >> up to suit my own development processes a bit as I'm more a Git/GitHub >> kinda guy. It would be great to keep the DNR domain and website. If >> I'm the only one working on things then I would prefer the issue >> tracker move over to GitHub with the repo to simplify / streamline >> things a bit. Ideally though I would prefer to do that sort of thing >> with some sort of community approval, and of course if there are a >> bunch of people who are happier with the current way things work then >> I'm also happy to talk about that too. >> >> So I'm going to put it out there as a proposal: >> >> 1) I'm willing to take over maintenance / development on DNR. I'm in a >> similar position to what Rob had recently - this won't be my full time >> work, it will have to fit in around stuff that actually pays the >> bills. However, as I said before we use DNR in commercial applications >> and in BrightstarDB so I at least have a some incentives to make sure >> stuff works ;-) >> >> 2) For my own ease of work I would like to transfer the DNR repo over >> to GitHub - this includes the issue tracker and, over time the wiki >> and possibly eventually the website too (the source code and issues >> would be the priority though). I would create a DotNetRDF Organization >> on GH that any other contributors would be free to join so the repos >> would be under something like github.com/DotNetRDF/.. >> <http://github.com/DotNetRDF/..>.. > >I definitely support that. I proposed the move to Bitbucket but ever >since I've moved to git and GitHub has only strengthened it's lead >position in open source community through ease of contributing, rich >features and 3rd party integrations. I think we should go that route, >with easier solution and CI setup. > >First things first though. Alas, as I said, I am not and likely won't >become a very active contributor but the least I could do is help with >rebooting DNR at GitHub. Be it through solution and CI overhaul or >moving wiki/issues/website to the new location. > >> >> 3) The project would keep the current MIT license. >> >> 4) I'm not in a position to actively maintain all of the different >> store integrations though (its quite a big ask to be constantly >> testing all of the different stores especially as some of them change >> quite frequently and require that weird-ass Java stuff ;-). I would be >> looking for volunteers to work on those and would probably split each >> one out into its own sub-project that can release at its own cadence. >> >> >> If anyone has any comments or opposition to that please raise it here. >> This is just a proposal and I won't be offended if people are against >> it or have other better ideas to put forwards! >> >> Rob, a couple of admin / ownership issues would arise here - these >> don't need to be actioned right now, I would just like to get an idea >> of what needs to happen if no one objects to the proposals above: >> >> a) Managing the dotnetrdf.org <http://dotnetrdf.org> domain - I'm >> happy to take over the cost of maintaining the domain and any hosting >> that you are paying for. Or if you would prefer to keep the domain >> that is cool too. >> b) NuGet releases - I think this should be as simple as you adding a >> new package owner so that we can keep the existing NuGet package names. >> c) VDS.Common - as this is one of the key dependencies for DNR it >> would be good to know what your plans are with that project. Is it >> also something that should be transferred over ? >> d) Less important but currently the assemblies are signed right? It >> might be good to transfer the existing private key, but again its not >> a big deal if you would prefer to keep that and I just create a new >> private key for the next DNR release. >> >> Cheers >> >> Kal >> >> On Tue, Apr 12, 2016 at 9:58 AM, Rob Vesse <rv...@do... >> <mailto:rv...@do...>> wrote: >> >> Kal >> >> Don't forget that you have commit privileges so you can of course >> continue to maintain the official repository yourself if you wish. >> Also I can give you or anyone else who wants it write access to >> the dotnetrdf.org <http://dotnetrdf.org> website, issue tracker etc. >> >> >> Rob >> >> From: Kal Ahmed <ka...@ne... >> <mailto:ka...@ne...>> >> Reply-To: dotNetRDF Developer Discussion and Feature Request >> <dot...@li... >> <mailto:dot...@li...>> >> Date: Monday, 11 April 2016 11:38 >> To: dotNetRDF Developer Discussion and Feature Request >> <dot...@li... >> <mailto:dot...@li...>> >> Subject: Re: [dotNetRDF-Develop] End of line >> >> Hey Rob, >> >> I'm sorry to see you go, and more sorry that I haven't be >> contributing as much as I would have liked to / should have. >> However, I do fully understand your position - I've been in >> the same place myself with my open-source projects. I would >> like the awesome stuff that you have done with DNR to live on >> in some form. From a my perspective I will at the very least >> work on a fork of DNR as my company has a bunch of tools and >> services built on the libraries. However, if others are also >> willing to step up I'd be happy to talk about carrying the >> project as an open-source effort. >> >> If anyone else on this list would like to discuss if/how the >> project proceeds, speak up now guys! >> >> Cheers >> >> Kal >> >> On Mon, Apr 11, 2016 at 10:51 AM, Rob Vesse >> <rv...@do... <mailto:rv...@do...>> wrote: >> >> Folks, >> >> So you may have noticed that there has not been any >> releases in a long time, and again you may have not since >> there is little to no activity here at all. >> >> Personally I no longer have the drive, time nor the >> capability (due to unforeseen health issues) to continue >> making any efforts to take this project forward or even to >> continue to maintain it. Therefore since no one else is >> helping out with this the project is for all intents and >> purposes dead. >> >> As a good friend in the open source community is fond of >> saying: >> >> There are three ways to participate in open source -hope, >> sponsor, contribute >> >> Unfortunately this project has never succeeded in building >> a community of contributors and has mostly relied on >> hoping someone else will do the work for them. I >> acknowledge that this is as much my failure to build a >> viable community as it is a failure of the community to >> get more heavily involved but unfortunately it leaves us >> in a situation where my stepping down essentially kills >> the project. >> >> Sorry to be leaving like this, >> >> Rob >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with >> Applications Manager >> Applications Manager provides deep performance insights >> into multiple tiers of >> your business applications. It resolves application >> problems quickly and >> reduces your MTTR. Get your free trial! >> http://pubads.g.doubleclick.net/ >> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 >> <http://pubads.g.doubleclick.net/gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532> >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> <mailto:dot...@li...> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> -- >> Kal Ahmed >> Director, Networked Planet Limited >> e: kal...@ne... >> <mailto:kal...@ne...> >> w: www.networkedplanet.com <http://www.networkedplanet.com> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with >> Applications Manager Applications Manager provides deep >> performance insights into multiple tiers of your business >> applications. It resolves application problems quickly and >> reduces your MTTR. Get your free trial! >> http://pubads.g.doubleclick.net/ >> gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532_______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> <mailto:dot...@li...> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with >> Applications Manager >> Applications Manager provides deep performance insights into >> multiple tiers of >> your business applications. It resolves application problems >> quickly and >> reduces your MTTR. Get your free trial! >> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> <mailto:dot...@li...> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> -- >> Kal Ahmed >> Director, Networked Planet Limited >> e: kal...@ne... <mailto:kal...@ne...> >> w: www.networkedplanet.com <http://www.networkedplanet.com> >> >> >> ------------------------------------------------------------------------------ >> Find and fix application performance issues faster with Applications Manager >> Applications Manager provides deep performance insights into multiple tiers of >> your business applications. It resolves application problems quickly and >> reduces your MTTR. Get your free trial! >> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z >> >> >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > >------------------------------------------------------------------------------ >Find and fix application performance issues faster with Applications Manager >Applications Manager provides deep performance insights into multiple tiers of >your business applications. It resolves application problems quickly and >reduces your MTTR. Get your free trial! >https://ad.doubleclick.net/ddm/clk/302982198;130105516;z >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
From: Ron M. Z. <ro...@ze...> - 2016-04-14 20:54:03
|
Hey Rob, As everyone else has said, I'm sorry to see you go and also sorry that I haven't been able to contribute or do much in a long while. I'm most sorry to hear of your health issues. All the projects I had using RDF have died or were forced to move to other technologies. Maybe I'll get to use it again someday. But thank you so very much for all you've done for the community and all the help you've given me over the past few years. Please let me know if there's every anything I might be able to do for you. Ron So you may have noticed that there has not been any releases in a long time, and again you may have not since there is little to no activity here at all. Personally I no longer have the drive, time nor the capability (due to unforeseen health issues) to continue making any efforts to take this project forward or even to continue to maintain it. Therefore since no one else is helping out with this the project is for all intents and purposes dead. As a good friend in the open source community is fond of saying: There are three ways to participate in open source -hope, sponsor, contribute Unfortunately this project has never succeeded in building a community of contributors and has mostly relied on hoping someone else will do the work for them. I acknowledge that this is as much my failure to build a viable community as it is a failure of the community to get more heavily involved but unfortunately it leaves us in a situation where my stepping down essentially kills the project. Sorry to be leaving like this, On Mon, Apr 11, 2016 at 5:51 AM, Rob Vesse <rv...@do...> wrote: > Folks, > > So you may have noticed that there has not been any releases in a long > time, and again you may have not since there is little to no activity here > at all. > > Personally I no longer have the drive, time nor the capability (due to > unforeseen health issues) to continue making any efforts to take this > project forward or even to continue to maintain it. Therefore since no one > else is helping out with this the project is for all intents and purposes > dead. > > As a good friend in the open source community is fond of saying: > > There are three ways to participate in open source -hope, sponsor, > contribute > > Unfortunately this project has never succeeded in building a community of > contributors and has mostly relied on hoping someone else will do the work > for them. I acknowledge that this is as much my failure to build a viable > community as it is a failure of the community to get more heavily involved > but unfortunately it leaves us in a situation where my stepping down > essentially kills the project. > > Sorry to be leaving like this, > > Rob > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > |