the most important part of an issue report is a minimal reproducer or
steps how to reproduce the issue. Since the main user base of an IDE are
devs, it is often possible to get good quality submissions in some cases.
It is really difficult to automate this. Telemetry can do only so much
and privacy/trust is also a concern there (you don't want your IDE to
upload your source code if there is a parsing error or take screen
shots, right?).
With the traditional submission process a user can decide what
information to provide and review logs/snippets etc before submission -
so the whole problem is completely avoided.
Since the user base of an IDE are devs, it is also likely that they have
a github account already. So this shouldn't be a big barrier if you
really want to submit a bug report.
And as Neil already alluded to: open source projects rarely have a lack
of issue submissions. There is no need to artificially inflate the issue
count with automated uploads [1].
Some open source projects go even a step further and automatically close
stale/inactive issues after a certain time period. Since inactive issues
are probably not interesting enough to be fixed by the community - no
need to keep them in the system forever.
best regards,
michael
[1] https://martinfowler.com/bliki/Datensparsamkeit.html
On 07.12.22 17:31, Sean Carrick wrote:
It's really too bad that NetBeans Project went with GitHub, instead of
GitLab...GitLab has a feature called "Service Desk" that provides a
unique email address to which bugs, RFEs, etc., can be email by
anonymous users, without them needing a GitLab account. In that
instance, NB would only have needed to change the private code of the
old bug reporter to redirect to the Service Desk email address...Just
an FYI for the future, maybe.
Sincerely,
Sean Carrick
Owner - PekinSOFT Systems
s...@pekinsoft.com
(309) 989-0672
On Wed, Dec 7, 2022 at 9:05 AM Neil C Smith <neilcsm...@apache.org> wrote:
On Mon, 5 Dec 2022 at 22:28, Greenberg, Gary
<ggree...@visa.com.invalid> wrote:
> It used to be a feature that allows to submit exceptions along
with some other info to Netbeans development team with a
> click of a button.
> Now you can only open notification and view the exception stack
trace and that’s it. Exceptions do occur regularly and I
> mostly ignore them. I did raise this question sometime ago and
was told that now I need to open JIRA ticket manually to
> submit any NB problem and supply code samples in Apache GIT.
The infrastructure for accepting issues in that way no longer exists.
It never existed at Apache.
NetBeans issues should be reported in the GitHub issue queue. There
is no JIRA access for users. You'll need a GitHub account to report -
https://github.com/apache/netbeans/issues
See also https://netbeans.apache.org/participate/report-issue.html
> IMHO it is bad idea and not acceptable for many Netbeans users
because
>
> It does take more time, which is hard to allocate in busy
development schedule.
You need to balance that with the time needed for the volunteer
NetBeans community, many of whom also have a busy development
schedule, to assess any reported issue. Yes, you may now need to
spend more time in order to provide all of the required information to
submit an issue. It's better than incomplete issue reports
languishing completely ignored. IMHO that is an even worse and
unacceptable situation for everyone.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
