Open Bug 1297025 Opened 9 years ago Updated 8 years ago

Create a new table to manage system requirements

Categories

(Websites :: Nucleus, defect)

Product:
Websites
Component:
Nucleus
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: Sylvestre, Unassigned)

Details

For now, system requirements are stored in the release tables. We should instead create a new table to manage them. We should have in this table, at least: * a code name (FirefoxwithSSE2). * the content of the system requirements (example: https://www.mozilla.org/en-US/firefox/48.0.1/system-requirements/) A system requirements can be used by several releases. A release can have only one system requirement! In the django admin view, we should be able to see all the versions using the system requirement. Except if this is trivial, we would not have to import all the system requirements into the table. Just do something like "if there is a systemRequierementId set, use it, otherwise, fall back on the system requirement field in the release table" The nucleus code is available here: https://github.com/mozilla/nucleus/ rna might have to be updated too: https://github.com/mozilla/rna/
Of course, we should also update the release view to be able to select the system requirement.
I would like to work on this bug.Can anyone help?
Sure, just ask your questions in this bug.
thanks for a reply..from where should i begin?
(In reply to Sylvestre Ledru [:sylvestre] from comment #3) > Sure, just ask your questions in this bug. thanks for a reply..from where should i begin?
Sorry but If you are a beginner, this bug might not be the best to start with.
(In reply to Sylvestre Ledru [:sylvestre] from comment #6) > Sorry but If you are a beginner, this bug might not be the best to start > with. Let's try it ...
(In reply to Sylvestre Ledru [:sylvestre] from comment #6) > Sorry but If you are a beginner, this bug might not be the best to start > with. Let's try it.Can you help me?
First thing is that you have to dig on your own. Comment 0 gives you all the necessary information to start
(In reply to Sylvestre Ledru [:sylvestre] from comment #9) > First thing is that you have to dig on your own. > Comment 0 gives you all the necessary information to start Thanks for it!
Hi I have follow the procedure give in github i.e https://github.com/mozilla/nucleus/ .I am about to complete it.Now what will be the next step .I have done a decent work in python.Can you please guide me..
You should create a new table to manage the system requirements.
hi ,i had setup the docker enviornment ,now moving to create table
Hi (In reply to Sylvestre Ledru [:sylvestre] from comment #12) > You should create a new table to manage the system requirements. Hi sylvestre,I have created a table for storing system requirements right now It has two fields one is code name and system requirements field(Char field).What else next i need to do?.Is we need to create new api in django rest framework for storing system requirements ?.I am litte confused in architecture of nucleus.
(In reply to Sylvestre Ledru [:sylvestre] from comment #12) > You should create a new table to manage the system requirements. hi,eagerly waiting for your reply.
You should import the previous system requirements in this table.
Hi, i am attending an open source module at university, and would like to be assigned to this bug.
Flags: needinfo?(sledru)
Sure, you should start and I will assign it to you when you will have a poc :) Thanks
Flags: needinfo?(sledru)
Can I work on this issue ?
Flags: needinfo?(sledru)
Sure, go ahead!
Flags: needinfo?(sledru)
Can you please check and confirm the workflow: 1: Create a new table inside Rna models for System-requirements. 2: Link it to the original Release table with a many-one relation. 3: Import the data into the table: System-requirements (*) 4: Update the Django admin view to incorporate the System-requirements table editing. 5: Update the Release table view to be able to select data from the System-requirements table. * I couldn't understand exactly, what you've stated regarding the import of all the System-requirements to the table. I couldn't find any System-requirement id field in the Release table, or maybe I've manipulated it in a wrong way. Can you please elaborate upon how we can update the data of the System-requirements table? Also, should I submit the partial codes on Github or Bugzilla?
Flags: needinfo?(sledru)
About 3, this is defined here: https://github.com/mozilla/rna/blob/master/rna/models.py#L46 Besides that, this sounds a great plan! :) github would be best. Pull request please!
Flags: needinfo?(sledru)
I'm not able to see my migrations when I change the rna models.py file. These are the steps that I followed: => built the nucleus project with docker-compose. This created an rna directory inside the usr/local/lib/python2.7/dist-packages/rna => Now when I make changes to this rna directory and run the command "docker-compose up" in the nucleus, it says no-migrations to apply. Can you help me with this? It's been a long struggle for me and I'm not able to move ahead with the work.
Flags: needinfo?(sledru)
Also, why is rna showing inside the unmigrated apps when I run python manage.py migrate?
I am sorry but I never used the docker image to start the build project :/
Flags: needinfo?(sledru)
I've created an initial code review pull request at https://github.com/mozilla/rna/pull/61 Please see the content of the SystemRequirements table.
Flags: needinfo?(sledru)
I replied there
Flags: needinfo?(sledru)
I need slight info about the creation of form for the System Requirement addition on the admin view. So, I was thinking of adding a dropdown list of available system requirements to choose from while choosing system requirements for a particular Release. So, should I make use of the code_names of the system_requirements in the dropdown menu? If not, which method should I use to, so that the user can choose from a list of system requirements while adding one in a release? Also, I've marked the date added in the System Requirements table to be autonow. Is this okay?
Flags: needinfo?(sledru)
Is this bug still needs to be resolved? Please check my progress on github, I'm almost up with the full code.
Pmac reviewed it (many thanks). (sorry, I don't know the answer to your question)
Flags: needinfo?(sledru)
Hi. I would like to work on this bug .
A beginner here. Anyone up for help?
Hi. If no one works on this bug, I would like to take it. I have one question, however, related to a presentation of release resource in REST API. I can hide the fact that requirements can come from "legacy" column in the release table or from a brand new separate table, so a client would get the same structure of the response as it gets now. But how POST to /rna/releases/ should work with regards to requirements?
if anyone is interested, you should finish the work on https://github.com/mozilla/rna/pull/61 (you can create a new PR but please preserve ownership of the previous commits)
Hey I'm looking for a good first bug to work on, is this bug still open and can I be assigned to it?
We are discussing about changing the whole structure, so, not sure we should keep that as a good first bug. Sorry!
Mentor: sledru
Whiteboard: [good first bug][lang=Python]
You need to log in before you can comment on or make changes to this bug.