Reproducible builds

dietercastel · 30 September 2019 18:27

I opened an issue on 'Reproducible Builds'. Let me know what ya'll think of this suggestion.

I'm looking forward to your feedback.

tessus · 30 September 2019 20:40

You are supposed to open a discussion about new feature requests here on the forum. Only, if they are accepted yoiu should open one on github.

If you had read the template, you would have known that feature requests on github without a link to the discussion on the forum are closed.

dietercastel · 8 October 2019 14:39

[meta]
Could you please detail exactly that then in your template, I don't want to be a bore but it says nothing about feature requests, enhancements, the opening or not opening of issues. "It's not for questions" is a bit vague imho. If you don't want issues opened, detail the process instead:

Something like:

DO NOT OPEN ANY NEW ISSUES HERE, ALWAYS OPEN AN ISSUE FIRST ON OUR DISCOURSE. AFTER BEING REVIEWED AN ISSUE ON GITHUB WILL BE OPENED.

Instead of:

The issue tracker is not for questions.

(I can only put two links so removed some links here)

Questions and Help

Links

Clear communication helps both parties really, and imho this was, and still is unclear to me. Improving that message will help reduce the amount of people like me misinterpreting it. Sorry for that.
[/meta]

tessus · 8 October 2019 23:06

I’m sorry, but what’s not clear? Do you see an option for feature requests? No? What could that mean? Most people would think that the issue tracker is not for feature requests, which I have stressed more than enough in the template, when there was still a feature request template (which was also ignored).

But maybe we can add more info to the template that shows up, when you click on Open a regular issue.

Btw, did you read:

github.com

laurent22/joplin/blob/master/CONTRIBUTING.md

# User support

The [Joplin Forum](https://discourse.joplinapp.org/) is the community driven place for user support, general discussion about Joplin, problems with installation, new features and software development questions. It is possible to login with your GitHub account. Don't use the issue tracker for support questions.

# Reporting a bug

File bugs in the [Github Issue Tracker](https://github.com/laurent22/joplin/issues?utf8=%E2%9C%93&q=is%3Aissue). Please follow these guidelines:

- Search existing issues first, make sure yours hasn't already been reported.
- Consider [enabling debug mode](https://joplinapp.org/debugging/) so that you can provide as much details as possible when reporting the issue.
- Stay on topic, but describe the issue in detail so that others can reproduce it.
- **Provide a screenshot** if possible. A screenshot showing the problem is often more useful than a paragraph describing it.
- For web clipper bugs, **please provide the URL causing the issue**. Sometimes the clipper works in one page but not in another so it is important to know what URL has a problem.

# Feature requests

Please check that your request has not already been posted in the [Github Issue Tracker](https://github.com/laurent22/joplin/issues?utf8=%E2%9C%93&q=is%3Aissue). If it has, **up-voting the issue** increases the chances it'll be noticed and implemented in the future. "+1" comments are not tracked.

As a general rule, suggestions to *improve Joplin* should be posted first in the [Joplin Forum](https://discourse.joplinapp.org/) for discussion.

This file has been truncated. show original

Topic		Replies	Views
Improve Github Issue Template Development	1	652	8 October 2019
Please post bug reports on GitHub Support	6	1082	3 March 2021
Reporting bugs on Github issue trackers of Joplin plugins and forks Plugins	1	154	16 April 2024
New to contribution Lounge	3	58	29 October 2024
Troubleshooting FAQ and collecting topic for contributing to Joplin codebase Development tips-and-tricks	16	2944	27 January 2021

Reproducible builds

Questions and Help

Links

Related topics