Hi Gary,

It's a genuine concern you just raised. But I'll rather the milestones for
the the two projects be spell out clearly and then we can pick two students
to work on them. I think we already have some proposals for the License
Submittal project that make mention of the including the License XML
editor. Adding that with Django the separate idea can be be developed on
the existing Online tool as Django apps, just to avoid the code overlap and
not spread resources unnecessarily.

Krys Nuvadga


On Thu, Mar 22, 2018 at 8:33 PM, <[email protected]> wrote:

> *Background*: The GSoC project idea Add New License Submittal Feature to
> Online Tool is quite popular with students
> <https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas#Add_New_License_Submital_Feature_to_Online_Tools>
> – at least 4 proposals are in progress for this one project.  Since we can
> only select one of the proposals, I would like to add another project idea
> of similar scope and usefulness to the community as an alternative project
> for students.  The deadline for submittals is coming up quickly – next
> Tuesday 27th!
>
>
>
> One concern I have with the proposal is there is some overlap in code
> functionality with the existing license submittal project idea.  I
> personally think it would be fine to have this overlap and allow some
> duplication of code for the two projects.  Once the projects are complete,
> we could have a separate task to refactor and reduce the duplication.
>
>
>
> *Action requested*: For the legal team – please review the proposal below
> and reply if you feel this tool proposal would be useful by end of day
> Friday.  For the technical team, please provide feedback if you feel this
> proposal has too much technical overlap with the existing proposals.
>
>
>
> *Proposal*:
>
> Add a License XML Editor
>
>
>
> The SPDX license list (see https://spdx.org/licenses/) is maintained by
> the SPDX legal team. The source for the license list is maintained in the
> SPDX license-list-XML github repository (https://github.com/spdx/licen
> se-list-XML). Making changes to the license requires manually editing an
> XML file which can be challenging for contributors not familiar with XML.
>
> An online program could be created which would take as input a license XML
> file uploaded from the client machine to the server.  The editor would
> allow editing of all of the XML fields as well as the optional and
> alternate text properties.  The editor would then save the changes and
> allow the updated file to be downloaded to the user’s client machine.  An
> optional feature would be to allow the input to be an existing license in
> the repository and automatically create a pull request with the changes.
> Another optional feature would be to allow copy/paste of the license XML
> text into a text pane rather than uploading/downloading the file.
>
> This project could be implemented in Python in the existing online tools.
> Skills Needed
>
> ·        Development skills in the Python language
>
> ·        Knowledge of Git
>
> ·        Understanding of XML
> Available Mentors
>
> Gary O'Neall <[email protected]> Rohit Lodha
> <[email protected]>
>
>
>
>
>
> -------------------------------------------------
>
> Gary O'Neall
>
> Principal Consultant
>
> Source Auditor Inc.
>
> Mobile: 408.805.0586 <(408)%20805-0586>
>
> Email: [email protected]
>
>
>
> _______________________________________________
> Spdx-tech mailing list
> [email protected]
> https://lists.spdx.org/mailman/listinfo/spdx-tech
>
>


-- 
krys Nuvadga
Piar, Inc.
_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech

Reply via email to