Ideas for contrib modules

Open
#111 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reading issue #102 and the linked discussion about contrib modules. Review the referenced Kivy Garden repositories and web2py's contrib approach. Done means the project has agreed on a concrete module namespace, publishing model, and implementation scope.

Written by the indexing model from the issue text.

Description

architecture enhancement
Some context:

As a #102 (partial) follow up, I'm actually comparing functionalities between web2py and py4web cause I'm migrating some services to the fastest 🎉 and newer py4web.

My thoughts about contribs modules:

Currently py4web doesn't have any contrib folder like web2py, and it lacks about features like pdf rendering or Recaptcha2.

What's going to happen in the future?

I've seen in https://github.com/web2py/py4web/issues/4#issuecomment-477875891 that contribs module are supposed to be present, so seems that py4web currently doesn't have any contrib module cause it's still a newborn-stage project and needs some time before contributors start creating some modules that could speed-up everyday devs life 😃 .
There's any idea about how to implement the contribs modules in py4web?

I think that somewhat like kivy's garden/flower implementation could be a great feature / idea in order to give contributors their own ability to publish contrib modules over a unique namespace and it's also a wonderful oppurtunity to take the core and contribs modules well separated.

What do you think about that?

Some reference links
https://github.com/kivy-garden/flower
https://github.com/kivy-garden/garden
https://kivy-garden.github.io/

Dominant language
HTML
Stars
319
Forks
144
Avg merge
6d 20h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from web2py/py4web

All issues in web2py/py4web

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.