Hi All, Although I still think and agree that organizing a couple of technical sessions regarding the codebase is a great idea, taking into account that it is being complicated to bring Rupert in (I can ensure he is quite busy), I would also like to encourage you to start getting your hands dirty. As any other complex project (and this one it is), it is not going to be easy to getting started, but 2-4 hours of Rupert explaining the technical details is not going to change that too much, mainly because 2-4 hours is only enough time for an overall overview.
So, ad Fabian said, you can give it a try to any of the currently open issues or just try to start implementing anything you are interested in. The project has also a developers mailing list where we can try to discuss and solve detailed technical stuff. Don't be shy :-) On Fri, Mar 31, 2017 at 10:36 AM Michal Krajňanský < michal.krajnan...@gmail.com> wrote: > Hi Stanbolers and Mr. Soroka, > > I was curious, if there has been any development in the organization of the > meeting. Would it perhaps make sense to create a doodle, so that anyone > interested can vote for the suitable time? If I can somehow help make this > meeting happen, I will be more than happy to. > > Cheers, > Michal Krajnansky > Research Specialist > Konica Minolta Laboratory Europe > http://research.konicaminolta.eu/ > > On Mon, Mar 20, 2017 at 2:50 PM A. Soroka <aj...@virginia.edu> wrote: > > > This is a nice précis of how to get involved with pretty much any Apache > > project. On one particular point: > > > > > * There is no technical barrier to start contributing to Stanbol. > > > > Well, no, not any unsurmountable technical barriers. But it is not an > easy > > code base to approach (I count over 230 Maven modules!). There are a lot > of > > important underlying technologies like JAX-RS, OSGi (and the slightly > > obscure Sling launcher system), and an extensive set of relationships to > > other projects (e.g. Marmotta, Solr, etc.). And Stanbol has a lot of > great > > functionality with which to become familiar! > > > > So my hope for a synchronous meeting is rooted in the desire for some > > "bootstrapping" discussion that could help people like me (who are ready > > and willing to do work) get to do that work with as little overhead as > > possible, while updating and writing documentation to help the _next_ > > "generation" of Stanbol contributors. > > > > --- > > A. Soroka > > The University of Virginia Library > > > > > On Mar 20, 2017, at 4:54 AM, Fabian Christ < > christ.fab...@googlemail.com> > > wrote: > > > > > > Hi Stanbolers, > > > > > > there have been some questions in the direction of how to start > > > contributing to Stanbol. Especially from the viewpoint of a company. I > > > would like to point to some basics here at Apache. > > > > > > * The ASF projects are about people and not so much about companies. > > > However, companies are very welcome to let their employees contribute > > > to projects during their working hours. > > > * There is no technical barrier to start contributing to Stanbol. For > > > people, who are not yet committers to the SVN yet, the process is to > > > file a JIRA ticket and attach a patch file to that ticket for desired > > > changes. A Stanbol committer has to pick this patch and apply it to > > > the code base. > > > * People who started to contribute to Stanbol and show interest will > > > be invited to become official Stanbol committers. > > > * All discussions about the project and its contributions have to > > > happen on the dev mailing list. There should be no discussions in some > > > other channel that are not archived or visible to the world. The > > > mantra here is "If it is not on the list, it did not happen." > > > > > > So everyone with interest in the Stanbol technology is very welcome to > > > start any technical discussion about improvements on the dev list, > > > file JIRA ticket, submit patches. This is the way the group of > > > contributors will grow. > > > > > > Best > > > Fabian > > > > > > -- > > > Fabian > > > http://twitter.com/fctwitt > > > > >
