| Summary: | [client] landing page task icons - legal issues | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Client | Assignee: | Susan McCourt <susan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, janet.campbell, mamacdon, mike.milinkovich |
| Version: | 0.2 | ||
| Target Milestone: | 0.5 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Susan McCourt
Boris, opinions? The initializr icon should use the "5 in the shield" as that is what's used in the favicon. Noticed this just now. I agree we shouldn't be putting their logos into our git repo without a CQ and acceptable license terms. Ideal scenario is those sites host the plugins in the long term. *** Bug 363108 has been marked as a duplicate of this bug. *** It was pointed out in bug 363108 that this doesn't look good when running disconnected. However if the idea is that plugins contributing to the welcome page really come from different domains I'm not sure how we can resolve this (maybe some kind of caching). I don't think this is too complicated. For the two that we have - github and initializr - I think it would be pretty simple. Yes, they would need CQs to track, but I think that all we need to do is get permission. We won't need any big license to be written. For githib, we just need to double-check that we conform to [1] and then write an email asking permission. Attach the answer to the CQ. For initializr, I guess we just send an email [2] to the author and ask his permission. If you want Janet or I to review the email, just let us know. Including references to these logos and the permissions could be included in whatever it is that Orion does for About files. I understand the goal that ultimately we may want the Welcome page comprised of contributions which are hosted elsewhere. Note, however, that if we do that it won't work in the case I reported, where you're trying to run Orion locally with no internet connection at all. [1] https://github.com/github/media#readme [2] http://www.initializr.com/docs (see "Contact" at the very bottom) It would be good to settle this for 0.4. Perhaps these icons won't even be on the main page, but if they are going to appear anywhere, we should sort out the legal issues. Assigning to Ken. (In reply to comment #7) > Assigning to Ken. I think I made it clear in comment #5 what Ken needs to do. Please let me know if you need any assistance from the EMO. Will do Mike The emails were sent, waiting on replies Processing a CQ for the Initilizr icon - received response from author Initializr icon completed this bug is now fixed as part of the work in bug 345622, even though the entire workflow (bug 378758) is not complete. In bug 345622, the landing page task icons are removed, and the tasks themselves are now automated in the navigator. Rather than using initializr to generate content, we generate HTML5 default content inside Orion. This will allow the disconnected case to work which was Mike's concern in comment 6. A disconnected user's experience would be something like: - go to the localhost index.html - see a very pretty login page if you weren't logged in yet. (bug 368739). Log in. - now you are looking at a navigator with big getting started task buttons (no icons) showing. You can press a button to generate HTML5 content without having to go to initializr.com. You could also upload a zip. The other buttons (import, clone git repo) require a network, but we aren't showing any missing icons, etc. for these tasks. |