> >> > >> Such issues cannot be reported via Apache JIRA as this plugin isn't > >> officially supported. Fork doesn't have "Issues" so I'm wondering how > >> to handle this: > >> - do not fork, just copy the repo > >> - use "Issues" of the original repo > >> - create a new "struts-plugins" repo and use it to host some plugins > >> (we can also move some rarely used plugins there e.g. GXP, SiteGraph) > > > > I would prefer the 3rd option. That gives us control and is quite > > flexible. But it makes it probably hard for users to figure out where to > > report issues. > > Third options means that we officially support it and we should use > our JIRA.
Yes, that is what puts us in control and gives us flexibility. You can also call it independence of original developer. > There is also question about donating the source code, not > sure if we can grab it and commit... > So it is not sure if we can use the fork created by Johannes? I guess it boils down to the question how well we can work with original developer and how much time he puts into this. Regards, Christoph This Email was scanned by Sophos Anti Virus
