In principle the current system works, but let me ask it differently as well, why track issues on one product (netbeans-website) in a repository (apache/netbeans) which doesn't contain any related content (i.e. netbeans <> netbeans-website) to fix and commit to?
I see it as being able to focus on documentation issues to the specific product and not clutter conflicting website specific issues where there is no real way of fixing them. Given my netbean work is done in my spare time (which is limited - I'm spending most of my spare time on rebuild nb python plugin) and with my limited knowledge, I'm not sure if I have the time and knowledge to commit to it but with help I may be able to help some with mentoring in the process, then maybe I could try to pick up some of that. Eric Bresie [email protected] On Fri, Aug 12, 2022 at 11:39 AM Michael Bien <[email protected]> wrote: > or let me ask this differently: If there would be an issue tracker, > would you like to manage it and help fixing issues there, and why is the > current system not sufficient with the in-page review banners? > > -mbien > > On 12.08.22 18:30, Michael Bien wrote: > > I don't think the website needs a user facing issue tracker right now. > > Pages which need reviews are already marked, links allow to edit the > > page and propose changes via PRs right away - it couldn't be much easier. > > > > tracking it via issues would just create redundant noise, its already > > tracked right on the page. > > > > Finding more issues is not the problem right now, fixing them is. Once > > we run out of issues we can open more issue trackers :) > > > > just my opinion of course - if anyone would like to maintain a second > > issue tracker and fix issues too, I am sure we can open one for the > > website. > > > > regards, > > michael > > > > On 12.08.22 18:05, Eric Bresie wrote: > >> While looking through issues (i.e. > >> https://github.com/apache/netbeans/issues/4491 ), while reviewing > >> content > >> on the github repository ( > >> https://github.com/apache/netbeans-website ) I > >> noticed that this repository does not have "Issues" enable. Assume > >> this is > >> tracked in the mainline netbeans project but was curious.... > >> > >> Should this be enabled so web site / documentation specific details > >> can be > >> tracked there instead of on the code repository issue? > >> > >> Eric Bresie > >> [email protected] > >> > > > >
