Skip to content
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

Managing lnksz's contributions #34

Open
11 of 15 tasks
lnksz opened this issue Aug 27, 2017 · 0 comments
Open
11 of 15 tasks

Managing lnksz's contributions #34

lnksz opened this issue Aug 27, 2017 · 0 comments

Comments

@lnksz
Copy link
Contributor

lnksz commented Aug 27, 2017

Soon I will finish my work on rivus (as far as my thesis goes), and still have a lot of pending PRs, I summarized the properties of them hoping to ease the process/decision of acceptance/merging.
@KSchoenleber

Fast ToDo:

  • Add labels like in urbs, so that Issues and PRs can be labelled. This would ease the sorting and handling of those. [urbs-labels]
    • Adding documentation/discussion labels where needed.
    • maintenance, bug, etc...
  • Define version milestones. (Now 0.1, which is the original. Alone BUGFIX for line_length() #13 should mean a version upgrade.) (See doc)

Pull Requests

As I restructured the project at the beginning, and that was already merged, the PRs mostly consist of self-maintained contributions. However, broader developments can rely on changes now pending in earlier pull-requests.

Sub Packages

#self-contained

Core Changes

#maybe-self-contained

Merge conflicts can arise, as these operate on the same file. But in different places, so should be ok, or solvable with minimal time investment.

Broad Changes

#relying-on-others

@lnksz lnksz changed the title Pull requests handling Managing lnksz's contributions Aug 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant