Re: [BuildStream] Create new containers-related and Python-related plugins repos



Hi,

On Thu, Oct 25, 2018 at 3:01 PM Chiara Tolentino via BuildStream-list <buildstream-list gnome org> wrote:
Proposal: Domain-specific repositories for container-related and
Python-related plugins
=======================================================================================

As discussed during the recent BuildStream Gathering, ideally
BuildStream core should remain small and 'general purpose' without
turning bst-external into a dumping ground/kitchen sink. The proposed
solution was to move domain-specific plugins out of core and/or
bst-external and keep them in separate repositories, each with their
own maintainer. These repositories would then have a clearer purpose
and the maintainer would be responsible for ensuring the stability and
reliability of these plugins.

Following this, I'd like to propose two new domain-specific
repositories: one for container-related plugins and another for
Python-related plugins.


Container plugins repository
----------------------------

This would contain the following plugins (which currently reside in
bst-external):
- Docker source [1]

And will eventually include such plugins as:
- Docker element
- OCI element [2][3]
- OCI source

+1.
 
Python plugins repository
-------------------------

This would contain the following plugins (which currently reside in
BuildStream core):
- pip source [4]
- pip element [5]
- distutils element [6]

In the future, this could be extended to include:
- sdist
- binary wheel

+1.

For each of these we should consider a list of seed committers, which is
likely the set of contributors to those plugins?

As this would introduce a breaking change, this should ideally be
merged before the release of BuildStream v1.4.

Please let me know your ideas regarding this proposal.

I'd like us to consider going further earlier and removing all but the import,
junction, and abstract elements from BuildStream itself and moving that to
a plugins repository.  We can still bundle these in the release if we want
to, but it sets us on the path of maintaining the plugins separate from the
core.  It also prevents future discussions on what plugins should be in the
buildstream repository, and which shouldn't.
 
Cheers,
Chiara

Cheers,

Sander
 
[1]: https://gitlab.com/BuildStream/bst-external/blob/master/bst_external/sources/docker.py
[2]: https://gitlab.com/BuildStream/buildstream/merge_requests/655
[3]: https://gitlab.com/BuildStream/buildstream/issues/349
[4]: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/plugins/sources/pip.py
[5]: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/plugins/elements/pip.py
[6]: https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/plugins/elements/distutils.py
_______________________________________________
BuildStream-list mailing list
BuildStream-list gnome org
https://mail.gnome.org/mailman/listinfo/buildstream-list
--

Cheers,

Sander


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]