Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / chexxor/purescript-documentation-discussion issues and pull requests
#73 - Discontinuing my contributions to this project
Issue -
State: closed - Opened by JordanMartinez over 5 years ago
- 2 comments
#72 - Consider template in a later phase
Issue -
State: open - Opened by chexxor over 5 years ago
#71 - Update State-of-PureScript-Documentation-2019.md
Pull Request -
State: open - Opened by chexxor over 5 years ago
#70 - Clarify "Learner's Phase" table
Issue -
State: open - Opened by chexxor over 5 years ago
- 3 comments
#69 - Create Documentation-Principles.md
Pull Request -
State: open - Opened by chexxor over 5 years ago
#68 - Header revising in context/narrative
Pull Request -
State: closed - Opened by chexxor over 5 years ago
#67 - Re-structure context/narrative to new ToC
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 2 comments
#66 - Update to new structure
Pull Request -
State: closed - Opened by JordanMartinez over 5 years ago
- 7 comments
#65 - Adopt Jordan's suggested document structure
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 5 comments
#64 - Update State-of-PureScript-Documentation-2019.md
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 1 comment
#63 - Note the few number of sources for "good" docs
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 2 comments
#62 - Analyze 'Principles of PS'
Issue -
State: open - Opened by JordanMartinez over 5 years ago
#61 - Don't merge - Exploration on document's final structure
Pull Request -
State: closed - Opened by JordanMartinez over 5 years ago
- 1 comment
#60 - Clarify the Purpose in the context/narrative
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 3 comments
#59 - Add "How to Write Technical Posts" guidelines to a document here
Issue -
State: open - Opened by chexxor over 5 years ago
- 1 comment
#58 - Add methodology overview to ReadMe
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 2 comments
#57 - Describe the tools used to build parts of this document
Issue -
State: open - Opened by chexxor over 5 years ago
- 1 comment
#56 - Create an Introduction document which explains the project and its structure
Issue -
State: open - Opened by chexxor over 5 years ago
- 1 comment
#55 - New learners section
Pull Request -
State: closed - Opened by JordanMartinez over 5 years ago
- 11 comments
#54 - Core contributors section
Pull Request -
State: closed - Opened by JordanMartinez over 5 years ago
- 3 comments
#53 - Why docs are lacking
Pull Request -
State: closed - Opened by JordanMartinez over 5 years ago
- 16 comments
#52 - Include 'Hard parts of Open Source' and 'Building Trust'
Issue -
State: open - Opened by JordanMartinez over 5 years ago
#51 - Review and revise context-narrative
Pull Request -
State: closed - Opened by chexxor over 5 years ago
- 9 comments
#50 - Write the Context/Narrative
Pull Request -
State: closed - Opened by JordanMartinez over 5 years ago
- 27 comments
#49 - Add Elm audience resources #44
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 1 comment
#48 - Add "Make leap from JS to PS" #45
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 1 comment
#47 - Add last item from MVI_Architecture
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 7 comments
#46 - All Interpretations - Continue Work via PR?
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 3 comments
#45 - Include 'make the leap from JS to PS' learning resource
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
#44 - Include Elm -> PS learning resources
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
#43 - Revise ecosystem incoherence
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 1 comment
#42 - Include Zeal/Dash offline docs idea
Issue -
State: open - Opened by JordanMartinez almost 6 years ago
#41 - Revise analysis of Hitchhiker's Guide to Elm
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 1 comment
#40 - Analyze PS documentation infrastructure, build tools, and other learning resources
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#39 - Red Flag: Should we improve PS Documentation _now_?
Issue -
State: open - Opened by JordanMartinez almost 6 years ago
- 3 comments
#38 - Review analysis of Wallowing-in-Despair
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 6 comments
#37 - Chronologically sort Index of Sources file
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#36 - Workflow question: PRs and merging them
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#35 - Change license to that used by PS documentation project
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 3 comments
#34 - No longer analyze 'Outsider's Guide to FP' book
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#34 - No longer analyze 'Outsider's Guide to FP' book
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#33 - Analyze 'On the ergonomics of compiler errors in FP languages like PS/Haskell'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#32 - Analyze 'Why is Elm more popular than PS'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#31 - Ask others to share their experience on learning PureScript
Issue -
State: open - Opened by JordanMartinez almost 6 years ago
- 6 comments
#31 - Ask others to share their experience on learning PureScript
Issue -
State: open - Opened by JordanMartinez almost 6 years ago
- 6 comments
#30 - Analyze 'Teach, don't Tell'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 4 comments
#29 - Analyze 'All Tweets'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#28 - Analyze 'exploring the mvi architecture with purescript puzzler'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#27 - Analyze 'Purescript vs ReasonML/Bucklescript in 2018?'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#26 - Create Index for Sources
Pull Request -
State: closed - Opened by chexxor almost 6 years ago
- 5 comments
#25 - Include Elm PS Differences document
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 8 comments
#24 - Top-level index of sources?
Issue -
State: closed - Opened by chexxor almost 6 years ago
- 2 comments
#23 - Possible copyright issues?
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 8 comments
#22 - Analyze 'Hitchhiker's Guide to Elm'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#21 - Clarify outcome of 'gather and interpret sources' phase.
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 12 comments
#20 - Post our likely 'work hours'?
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 6 comments
#19 - Analyze Reddit discussion around 'What nobody tells you about documentation'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#18 - Analyze 'What nobody tells you about documentation'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 7 comments
#17 - Analyze 'Wallowing in Despair'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#16 - Include date of source in file name
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 7 comments
#15 - Analyze source: 'Elm 0.19 Broke us - Comment'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#14 - Encapsulating Twitter File?
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#13 - Payment Wall: Vue-HN
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#12 - Convert current "All.md" sources into own files
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#11 - Context or Narrative planning
Issue -
State: open - Opened by chexxor almost 6 years ago
- 18 comments
#10 - Change the Source's terms and definition file into a ReadMe file for its corresponding folder
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 4 comments
#9 - Define *what* we are finding sources for
Issue -
State: closed - Opened by chexxor almost 6 years ago
- 4 comments
#8 - Separate "Sources" into separate files
Issue -
State: closed - Opened by chexxor almost 6 years ago
- 4 comments
#7 - Defining workflow
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 9 comments
#6 - Defining source formatting
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 7 comments
#5 - Analyze 'How do we avoid ecosystem incoherence in the future?'
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#4 - Analyze 'The State of Things' source
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 1 comment
#3 - Issue Labels to use for tracking issues/content
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 3 comments
#2 - Separate content into own file
Pull Request -
State: closed - Opened by JordanMartinez almost 6 years ago
- 2 comments
#1 - Initial Steps before Approach
Issue -
State: closed - Opened by JordanMartinez almost 6 years ago
- 13 comments