Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Community feedback needed for project's development guidelines. #805

Closed
@fmv1992

Description

@fmv1992

Dear python-mode community,

I've been participating on this project in the background whilst developing my
own views of pymode at my own fork.

I've seen some good issues and points being brought up occasionally by other
users and I think this is a good oportunity to settle on some 'rules' and
practices for this project. The idea is to provide clearer guidelines on
contributing, future directions, etc.

So now its the time to speak up.

After our conclusions on this topic I'll commit myself to be more active and
assertive in closing/accepting pull requests.

So from my part I say we must have some sort of testing before accepting PRs.
I will put a draft on this topic later on. You can check it out here:

I'm marking people with recent activity below:

Conclusions

PRs

  • Should be tested before accepted (open to discussion on methodology).

Python code

  • Should conform to PEP8 and PEP257 (open to discussion).

Important feature requests

  • Priority:
    • Improve python-mode's communication (including our one-liner slogan and our
      readme.rst).
      • Redesign our slogan (make it more IDE-like).
      • Redesign ourreadme.rst.
    • Move third party libraries to submodules.
      • Advantages:
        • Provide modularity for our code base.
        • Moves and unnecessary burden of keeping the code base of different
          projects up to date.
        • Allow users to handpick their preferred versions of each library.
      • Disadvantages:
        • Forces users to issue and additional git command.
    • Cleanup libraries and huge codebase onpymode/libs.
    • Create a roadmap of python libraries that we want to include.
      • We should have a clear line on what to include and not to include,
        specially because adding up libraries probably would give diminishing
        returns (there is some overlap between them).
  • Non priority:

Contributors

  • Permanent contributors should be added after some time of steady
    participation on this project (clarification needed).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp