New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chiefr integration - distributed contribution model for searx #1029

Open
wants to merge 2 commits into
base: master
from

Conversation

Projects
None yet
2 participants
@asciimoo
Owner

asciimoo commented Sep 7, 2017

Hello,

I'd like to try to decentralize the contribution model of searx because of the following reasons:

  • Reduces the load of maintainers
  • Increases the responsiveness if a contribution arrives
  • Explicitly defines ownership of project parts (segments)
  • Experimenting is always good =)

I've created a tool (https://github.com/asciimoo/chiefr) to support the above idea.
Chiefr requires to define a maintainers file which contains all information about the maintainers and resources of project segments. I already created a minimal .maintainers.ini file and added some segments, but it is far from complete.

Please comment, if you have any thoughts about the idea or you want to be a maintainer of a segment of searx, and I'll update the maintainers file. Segment can be any set of files (except empty set) in the repo, even a single engine or just a function.

@dalf

This comment has been minimized.

Show comment
Hide comment
@dalf

dalf Sep 7, 2017

Collaborator

What is the process to merge in asciimoo/searx ?
Make a huge PR from time to time ? as they arise ?

So I should move #1025 to my fork ?

Collaborator

dalf commented Sep 7, 2017

What is the process to merge in asciimoo/searx ?
Make a huge PR from time to time ? as they arise ?

So I should move #1025 to my fork ?

@asciimoo

This comment has been minimized.

Show comment
Hide comment
@asciimoo

asciimoo Sep 8, 2017

Owner

What is the process to merge in asciimoo/searx ?
Make a huge PR from time to time ? as they arise ?

It's totally up to us. If a maintainer receives or writes some code which adds value to searx, then she/he can submit it to the main repo.

So I should move #1025 to my fork ?

Yes, that would be the proper way in the future, but I think, it's not necessary to put any extra effort to change previous contributions to fit to this model, so it's ok here.

Owner

asciimoo commented Sep 8, 2017

What is the process to merge in asciimoo/searx ?
Make a huge PR from time to time ? as they arise ?

It's totally up to us. If a maintainer receives or writes some code which adds value to searx, then she/he can submit it to the main repo.

So I should move #1025 to my fork ?

Yes, that would be the proper way in the future, but I think, it's not necessary to put any extra effort to change previous contributions to fit to this model, so it's ok here.

@dalf dalf added the meta label May 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment