Can we merge twotp into Twisted proper?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@oubiwann reported |
|---|---|
| Trac ID | trac#5569 |
| Type | enhancement |
| Created | 2012-03-26 00:13:26Z |
Thomas' work on twotp would be a general asset to Twisted users, providing interoperation with Erlang code/projects. Erlang is well-established as a standard tool in the world of concurrent programming, so this seems less of a risk than it might have been 4 years ago.
What's more, ticket #5565 could greatly benefit from this work, making our lives easier in the process.
What would it take to make this happen?
Searchable metadata
trac-id__5569 5569
type__enhancement enhancement
reporter__oubiwann oubiwann
priority__normal normal
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__
time__1332720806000000 1332720806000000
changetime__1332765880000000 1332765880000000
version__None None
owner__
cc__therve,glyph,exarkun
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing twotp's existing work and linked issue #5565, then determine what merging it into Twisted proper would require. Done would mean an agreed integration scope and a completed merge that supports the described Erlang interoperability. The issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, python
- Domain
- backend, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100