Search results

== Technical Team Report == * Proposals floating around on the technical mailing list.

==Technical Team Report== ==Business Team Report==

** Team will set cutover date and notify people of it * Process to add licenses to list

* Peter (Licensable incorporated into Package) from mail list. ...ems rather than marketing to people. Ed wants to have input from technical team into agenda.

== License List == ...d/resource for referring to licenses. Take-away of this is the the License List is shaping up to be an "entry point" from SPDX generally, i.e. easier to ad

The meeting discussion was focused on the SPDX "license list". ...ocess for adding new licenses to the list should be forwarded to the wider team for review. That proposal is attached below.

== Technical - Kate == == Legal Team - Jilayne ==

== Business Team Report - Jack/Scott == == Legal Team Report - Jack ==

== Tech Team Report - Kate == *** Can still contribute ideas

...http://wiki.spdx.org/view/Technical_Team/Ideas_List for a list of project ideas. ...gories, you must choose one. Used to help students filter the organization list.

...the technical and legal teams. The focus of this effort is for recording ideas and considerations about improving machine detection and recognition of lic * Matching Guidelines: http://spdx.org/spdx-license-list/matching-guidelines

* 11-11:30 License expression (joint tech, legal) – List of problems (not solving) * 11:30-12:00 (joint tech, legal) XML tooling for license list – Review plan, make sure we’re in sync on the next steps

* [https://spdx.org/using-spdx License List and Short Identifiers] ...oup. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could joi

...on, the tooling and problems we face are complex and should provide a good technical challenge for the student. ...ns tend to be made by consensus. The spec itself is written by a technical team with input and support from business and legal teams. Although much of the

* Discussed better documentation for license list machine readable files – Gary to propose language * Kate has started the process of moving ideas from the google docs to specific issues in github

** One repo for all SPDX with folders for each team * Santiago will share a doc with the linkage profile ideas

...tyle="font-size:150%">'''Welcome to the 2020 SPDX Community Bridge Project Ideas Page'''</span> * [https://spdx.org/using-spdx License List and Short Identifiers]

Past year Project Ideas for GSoC projects ..., additional issues can be taken on to create a full GSoC project (see the list below).