librecores / librecores-web Goto Github PK

mention mailing list, github, etc.

As a GitHub user, I want to add project hosted on the external organization (e.g. openrisc/mor1kx). Now I cannot do it from the web interface.

Option 1:

• Add a plain-text field for user/organization name

Option 2:

• Poll user PUBLIC organization membership
• Provide list of organizations
• For the selected organization retrieved list of repositories, to which the user has write access (should be enough to consider him as contributor). Or admin access...

A LibreCores organization is, similar to GitHub organizations, a collection of projects. They can be maintained by a group of people (a team) and serve as a "namespace" for the contained projects.

Requirements:

• User management #8, #9
• Create organization

As a follow-up to discussion with @wallento, we wiould like to setup a Docker Hub organization, which would store Docker images we use for automation of Librecores and EDA tools we use.

TODO:

• Setup organization
• Move some Docker images we use to this organization
• Add @wallento and maybe others as owners
• Add documentation to the internal Wiki

Show all data from the registration

I would like to get several sample projects posted on LibreCores staging. It would be useful for demos of LibreCores CI integration in #45.

Desired projects:

• wb_sdram_ctrl
• sockit
• wb_bfm
• mor1kx
• OPTIMSoC (a couple of configurations, for which we need a CI)

Test at http://stage.librecores.org/login

Planet LibreCores aggregates blog posts from many sources into one page. To add a page, blog owners should either open an issue here on GitHub, or write us an email at [email protected]. This process needs to be documented on the site.

Requirements

• license choice documentation
• source code hosting documentation

Look into the requirement of having proper terms of service.

Andrew Back had some ideas, Wordpress might have CC-licenses TOS that we can reuse.

Currently we search projects directly in MySQL. For a better search experience, we should move to Apache Solr or similar solutions, which then enable good result ranking, faceted search, etc.

Example implementation in Symfony: Packagist (https://github.com/composer/packagist)

Currently especially the homepage (https://librecores.org/) doesn't look good on mobile devices.

1. Figure out how we can reduce the content to be mobile-friendly. Especially the pictures (engage/code/share/reuse/learn) need to be reduced in size or left out completely.
2. Modify the HTML/CSS code using the Bootstrap provided CSS classes (http://getbootstrap.com/css/) to realize the idea.
3. Create a patch for the librecores-web repository to incorporate the changes into the site.

Report from google pagespeed:

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 325.5KiB (74% reduction).

Compressing https://www.librecores.org/css/app.css could save 159KiB (83% reduction).
Compressing https://www.librecores.org/js/app_body.js could save 139.4KiB (68% reduction).
Compressing https://www.librecores.org/img/home-cat-3.svg could save 6.9KiB (69% reduction).
Compressing https://www.librecores.org/img/home-cat-1.svg could save 5.4KiB (69% reduction).
Compressing https://www.librecores.org/img/home-cat-5.svg could save 4.1KiB (63% reduction).
Compressing https://www.librecores.org/img/home-cat-2.svg could save 3.9KiB (68% reduction).
Compressing https://www.librecores.org/img/home-cat-4.svg could save 3.4KiB (67% reduction).
Compressing https://www.librecores.org/img/logo_small.svg could save 3.4KiB (70% reduction).

It's still the old logo

As a minimal valuable feature we need:

• - Embedded Build Status Pointing to the last branch
• - Hyperlink to "Setting up CI for your project" if the CI is not integrated

Otherwise the cert will expire

Hi,

on Ubuntu 15.04 the current vagrant setup led me to some issues:

• Don't run from ecryptfs home folder (cannot be NFS exported)
• The dev-vagrant.secrets.yml of ansible does not exist
• sudo apt-get update must be run in the machine before installing ntp
• There is a permission denied for /var/www/site/. Changing from NFS in the Vagrantfile solved it.

Now Vagrant completes, but RuntimeException in ClassCollectionLoader.php line 239:..

Best,
Stefan

Hi,

on Ubuntu 15.04 the current vagrant setup led me to some issues:

• Don't run from ecryptfs home folder (cannot be NFS exported)
• The dev-vagrant.secrets.yml of ansible does not exist
• sudo apt-get update must be run in the machine before installing ntp
• There is a permission denied for /var/www/site/. Changing from NFS in the Vagrantfile solved it.

Now Vagrant completes, but RuntimeException in ClassCollectionLoader.php line 239:..

Best,
Stefan

To avoid naming clashes in the URL, prevent all user/org names that we use as regular URL: "unassigned", "new". others?

.. is in the title.

I think it looks better if the top logo also looks better with full colors. Can you maybe put up the svg of the current logo?

Projects should be added tags.

I think the tags should be moderated, meaning the user can choose from pre-defined tags. Adding a new tag does not add this to the global index before a "moderator" added it (to avoid thrashing of the index).

Check if/what we need in terms of cookie policy notifications to our users.

Do initial load testing of the different parts of the site (homepage, search, project listing) to get an initial idea about our load handling capacity.

List projects alphabetically, filter by tags.

I like the idea of selected projects, maybe as a special tag-filter that is then advertised on a special timeline on the left or so.

Requirements:

• User registration: #8
• User login: #9
• Permissions system
• Project creation: #28

Every user/org should be associated with a picture.

Give users the option:

• pick existing one from gravatar (default)
• upload an individual image

Requirements:

• license usage documentation: what implications do the licenses have?

Currently supported:

• GitHub login
• Google login
• site login

Test at http://stage.librecores.org/register/

currently we use google analytics, but we should look into more privacy-preserving options.

Possible criteria:

• works with/without client-side (to also count users with adblock/tracking protection enabled)
• integration with custom "conversion goals" (interaction with the site, downloads, etc.)

Possible solutions:

• Piwik
• server-only solutions (follow-ups to the discontinued modlogan?)
• others?

Requirements:

• license choice documentation
• source code hosting documentation

Preview at http://stage.librecores.org/planet

Currently the hierarchy in librecores ends with "projects", which can be HW or SW or combined works.

We should introduce "IP Cores" (or named similarly) as a subhierarchy below a project (1:n).

Design idea:

• 1 directory == 1 core

Discovery options:

• automatically parse fusesoc core files (i.e. directory of .core/.system) file is "core directory"
• automatically parse ipxact files (similar to fusesoc above)
• let users manually cores by specifying the top-level core directory & additional metadata

Open Questions:

• does directory == core work for common projects out there? double check with some common projects.
• what metadata is minimally required/wanted per core?
• what data can we parse automatically in a generic way, what data is coming from fusesoc core file/ipxact files/..., and what needs to be entered manually?

Several services like DockerHub use Gravatar to display logos.
It would be great to setup Gravatar account for [email protected], so we will be able to retrieve logo from it.

We need some common teams on GitHub in order to streamline the work.

My proposals (based on what We have in Jenkins project):

• admins - People with admin access
• contributors - People who have write access to the org
• copy-editors - For reviewing the content changes (e.g. allows CCing people in PRs)
• bots - Automation bots with read-only access

Requirements:

• Project settings page
• Project team members editing

Include automated cert installation from letsencrypt in ansible

During development, we want to use test-data inside the database which allows us to quickly test features. Fixtures insert this kind of data into the DB through the actual objects (entities) which are used in our business layer.

Right now, we "cheat" by inserting a SQL-dump directly into the DB (this one: https://github.com/librecores/librecores-web/blob/master/sql/dev_fixtures_site.sql). This approach breaks whenever the entities change. So we should switch to proper fixtures, as described in http://symfony.com/doc/current/bundles/DoctrineFixturesBundle/index.html.

Tasks here:

• Get the fixture system working by integrating the correct bundle.
• Add fixtures which add
  • at least one test user
  • at least one organization
  • at least two test projects
• document the test user and passwords in the development documentation (doc/)
• (optional, just as Philipp otherwise) Adjust the Ansible deployment code to execute the fixtures and not insert the DB dump.

This bug has been marked as a "good first bug". If you're interested in working on it, have a look at the developer documentation at http://librecores-web.readthedocs.io/en/latest/ and comment on this bug or contact the listed mentor for more details. The mentor will be available to help you complete this task.

Mentor: @imphil
Required Skills: PHP, Symfony, a bit of Doctrine/database knowledge

As a newcomer developer, I would need to get more info about the process. E.g.

• Against which branch should I create pull requests?
• How do the changes get promoted to production? Is it a manual or automatic flow?
• How does CI work? (It does not work right now - https://github.com/librecores/librecores-ci/issues/17 )

We need properly styled error pages (404, 500, etc.)

Ideas:

• Show users where to get information from.
• Provide aggregated information from the community.
  • Automated aggregations:
    • Blog planet #5
    • Twitter feed with relevant twitter users
  • Editorial:
    • "Community newsletter": posted in blog or sent out per mail (example: https://news.opensuse.org/)

Now we use librecores-web, but it's a bit confusing since it has it's own branching system