If I understand things correctly we need to get code grant regardless of the license. In that case the willingness of authors to give them is more important than current license.
Technology wise, I would vote for solution that is not tied to particular relation type on the database and application layer (on the other hand, some per relation type UX optimizations are probably desired). Getting from system-only provided relation types to user-defined ones is then a small step. Peter On 3 April 2013 18:24, Andrej Golcov <[email protected]> wrote: > > I did not look at the TicketLinks solution when starting work on the > > MasterTicketsPlugin, so maybe I should give that a closer look. If it is > > the better candidate, we should go that with it. > That would be great. The decision should be very well elaborated. > > What I wanted to emphasize is that possibility of having code in BH > repository is quite big benefit that will simplify versioning, upgrade > and installation process. >
