What is an issue?
An issue is a term used to cover any concern, query, request for change, suggestion or off-specification raised within a development project of open-source software (OSS) or semantic interoperability assets. Any registered user of the platform can submit an issue, even without being member of the OSS or asset project. Only projects owners and developers can assign an issue to other members. An issue can be modified by developers, project owners as well as members assigned to the issue.
How can I find a particular issue?
The issue list offers two features to search for a particular issue:
- Keyword search: by filing in the “search for” field, users can provide keywords
- Search filters: by setting the right filters in the “Status”, “Priority”, “Category”, “Version”, and “Component” fields.
The global search feature of the platform also allows retrieving issues across multiple projects.
Who can view an issue?
Any registered users can view an issue.
How to view an issue?
To view an issue:
- Click on the project for which you want to see the issue;
- Click on the “Issue” menu item on the left of the page;
- A search tool and a list of issues will be displayed;
- Use the search tool to find the issue you want to see ;or
- Click on the issue name for entering in the issue you want to see;
- Once you have clicked on the issue name, the issue page will be displayed.
What is displayed on this page?
This page lists the following information for an issue:
- Project: Name of the project
- Version: Project version
- Component: The concerned component type
- Category: The category of the issue
- Priority: The priority of the issue
- Assigned: The software member assigned to this issue
- Status: the status of the issue
- Identifier
All comments and status changes to an issue are listed in chronological order of changes.
Edit an issue
Who can edit an issue?
- Any project member can edit his or her own issues. Modifying an issue is done by adding a comment to it.
- Only the project owner can fully edit issues (e.g. change the status or priority) once created by another project member.
- Each member of a project can take up an issue (assign it to himself) if the issue is unassigned.
- Developer or project owner can assign an issue to any other members.
How to edit an issue?
To edit an issue:
- Click on the project for which you want to edit the issue;
- Click on the “Issue” menu item on the left of the page;
- A search tool and a list of issues will be displayed;
- Use the search tool to find the issue you want to edit ;or
- Click on the issue name for entering in the issue you want to edit;
- Click on “edit” at the top of the page;
Remove/Delete an issue
Who can delete an issue?
Only author of an issue, the project owners, or the facilitators have the right to delete an issue.
How to remove an issue?
In the ‘edit’ mode, an issue can be removed by clicking the ‘delete’ button at the bottom of the page.
Comment an issue
Who can comment on an issue?
Any registered user can comment on an issue
How to comment on an issue?
- Navigate to the issue on which you want to comment;
- Enter your comments in the form at the bottom of the page;
- Press “Submit”.
See also Naming of concepts Software Project - Software Asset - Software Distribution
https://joinup.ec.europa.eu/asset/adms_foss/issue/naming-concepts-software-project-software-asset-software-distribution
I am not sure I understand why there can be an ambiguity between a Software Project and a Software Product. Can you give an example?
In natural language, project might be quite different from product. I have looked up the following definitions in the Cambridge Online Dictionaries:
I think that a product can be seen as the result of a project. Both concepts might be quite different.
In the RDF Schema, Software Project (admssw:SoftwareProject) is represented as a subclass of doap:Project, which in turn subclasses foaf:Project. I am not sure whether it is desirable to extend the meaning of admssw:SoftwareProject to include software products.
The thing is some people may be interested in characteristics of projects and others in characteritics of software products. As we haven't splitted the 2 in 2 different classes (for good reasons given the use cases we have), I feel better to make this choice explicit rather than let some implicit assumptions to be rediscovered on the future user's side.
We are truely discussing semantics here, this is very important. In my view, the meaning of 'Software Product' has more similarity with a 'Software Package' than with the software project. I see a 'software product' as the result of the software project. Would you agree with that? It can be helpful to again refer to the example of the Apache HTTPD Server.
I gave this issue some more thought and maybe I understand your concern. Sometimes, the project organisation behind a software is unclear. For example, LibreOffice, is rather a product suite than an actual project consisting of releases.
Would the following amendment to the definition of "project" address your concern?
"A Software Project is a time-delimited undertaking with the objective to produce one or more software releases, materialised as software packages. Some projects are long-running undertakings, and do not have a clear time-delimited nature or project organisation. In this case, the term ‘software project’ can be interpreted as the result of the work: a collection of related software releases that serve a common purpose."
The above-mentioned definition was added to the v1.00 specification.
"A Software Project is a time-delimited undertaking with the objective to produce one or more software releases, materialised as software packages. Some projects are long-running undertakings, and do not have a clear time-delimited nature or project organisation. In this case, the term ‘software project’ can be interpreted as the result of the work: a collection of related software releases that serve a common purpose."