Hello. 2020-06-01 22:18 UTC+02:00, Amey Jadiye <ameyjad...@gmail.com>: > Thanks for all the information/support guys. I dug into the archives and > found this[1] is the most recent interest shown by someone in > commons-graph. > even created a Jira[2] with lots of digestible information and todo already > but never progressed anymore. looks like maintainers left it here[3] with > no more progress. > > I used the existing commons-graph 0.1-SNAPSHOT and basic things look good > to me however need more things for my project and I found them in some > other OSS libs. I will be happy to see commons-graph graduated and see it > as the proper component, with my free time I will be working on this for > the next couple of weeks. I see the problem of graph being not on GitHub > though, I hope communication on Jira will suffice and effective to > communicate the patches (as graph is on svn).
You can always post a new message with the specific subject of moving it to git, in order to elicit opinions and, maybe, conditions. > > I see some 16 Jiras open right now in the sandbox[4] so I will pick up some > of them. I like the idea to compare the commons-graph with other libraries > and that makes roadmap to have all the features plus some more which are > not even in them. > > Now to start with I wanted to clear little confusion with what is released > and what's not, I see two releases of commons-graph on maven central[5] it > shows apache feather on it not sure if commons PMC released it with fork? > versions are 0.8 and 0.8.1 however site[6] shows just a 0.1-SNAPSHOT. I > went further to compare code decompiled from maven central jar(0.8.1) with > what's in svn(0.1-SNAPSHOT) *differences are huge*, leaving it. and > focusing on whats on svn. > > since the commons-graph is not as huge as some of the other commons > projects to be modular at this point. we should progress it with a single > module and after it stabilized in proper we can think of modularization. IMHO, it is preferable to make the component modular sooner (while it is relatively small) rather than later. As this will require to determine which parts need to belong together and the (acyclic graph of) dependencies, it will probably help improve the design. > let me know your opinions please. In the list of projects that use a graph abstraction, there is "Commons RDF". I guess that it would be interesting to see whether/how it could depend on "Commons Graph". Regards, Gilles > > [1] https://markmail.org/message/2xrwjomgkhlxsezm > > [2] https://issues.apache.org/jira/browse/SANDBOX-458 > > [3] https://markmail.org/message/niudr4rdz46sjis2 > > [4] > https://issues.apache.org/jira/browse/SANDBOX-458?jql=project%20%3D%20SANDBOX%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20graph%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC > > [5] https://mvnrepository.com/artifact/commons-graph/commons-graph/0.8.1 > > [6] https://commons.apache.org/sandbox/commons-graph/ > > Regards, > Amey Jadiye > > On Sun, May 31, 2020 at 10:22 PM Matt Sicker <boa...@gmail.com> wrote: > >> I have a vague interest in this library as Jenkins includes a bunch of >> graph logic for scheduling builds and such. It'd be nice to use a >> proper graph API someday. :) >> >> On Sat, 30 May 2020 at 19:34, Bruno P. Kinoshita <ki...@apache.org> >> wrote: >> > >> > Hi Amey! >> > >> > >> > >> 3. Any pending work or jiras available which I can help to graduate >> commons >> > >> graph? this is not available >> https://issues.apache.org/jira/projects/GRAPH ? >> > > >> > >Strange; again maybe the reason is in the ML archive. >> > >> > >> > I believe projects in the Sandbox use the common JIRA project >> > "SANDBOX": >> https://issues.apache.org/jira/projects/SANDBOX >> > >> > >> > And each component has a component under the SANDBOX project. The graph >> issues are under the graph component: >> https://issues.apache.org/jira/browse/SANDBOX-460?jql=project%20%3D%20SANDBOX%20AND%20component%20%3D%20Graph >> > >> > >> > Coincidentally, I also am working on a project with graphs, and >> yesterday started looking for cyclic graph unfolding algorithms to do >> some >> experiments. Even though my project is in Python, I was going to look at >> the commons-graph to see if there was any useful code there. >> > >> > >> > >> > Also, I **think** someone mentioned something about bringing graph >> algorithms to commons-collections. It might be worth checking if there's >> any overlap work in collections&graph. >> > >> > >> > >> > Cheers >> > >> > Bruno >> > >> > >> > On Sunday, 31 May 2020, 1:12:56 am NZST, Gilles Sadowski < >> gillese...@gmail.com> wrote: >> > >> > >> > >> > >> > >> > Hello. >> > >> > Le sam. 30 mai 2020 à 14:12, Amey Jadiye <ameyjad...@gmail.com> a écrit >> : >> > > >> > > Hi All, >> > > >> > > I'm working on an interesting project which uses Graph, I knew there >> > > is >> > > commons-graph available and I'm trying to use it. I have a couple of >> > > questions. >> > > >> > > 1. Why graph in the sandbox? >> > >> > Probably because work stopped before a first release. >> > >> > It might be worth digging into the ML archive in order to >> > know why that happened. >> > >> > > any plan of releasing it with 1.0 ? >> > >> > No. But you may come up with one. :-) >> > >> > > 2. I don't see its repo on GitHub thus I cant contribute a >> > > few improvements/additions I'm thinking? >> > >> > You could install and use Subversion, providing patches >> > through JIRA. >> > >> > > any plan of moving from svn to git? >> > >> > IMHO not before we know the answer to your first question. >> > >> > > 3. Any pending work or jiras available which I can help to graduate >> commons >> > > graph? this is not available >> https://issues.apache.org/jira/projects/GRAPH ? >> > >> > Strange; again maybe the reason is in the ML archive. >> > >> > Best, >> > Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
