Skip to content

Commit 2d67fc9

Browse files
more
1 parent f169ec3 commit 2d67fc9

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

proposal.Rmd

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -101,19 +101,23 @@ to open source development.
101101

102102
## Commitment
103103

104-
I will take the lead on the project and spend a one day per week on this project (typically Friday).
104+
I will take the lead on the project and spend one day per week on this project (typically Friday).
105105

106-
The time will be used for implementation, testing, documentation and community engagement.
106+
The time will be used for design, implementation, testing, documentation and community engagement.
107107

108108
# Project Milestones
109109

110110
## First iteration. $25k
111111

112112
This is the main lump of technical work on this project. This is when `ergo` starts to
113-
materialise as a development time R package.
113+
materialise as a development time R package. I will take the necessary time to
114+
produce frequent updates on the progress as blog articles, and engage the
115+
community as much as possible to ensure that `ergo` is aligned with the
116+
expectations of features and simplicity.
114117

115-
By design, `ergo` is only needed by package developers. End users of a package that contains
116-
code generated by `ergo` do not need to have `ergo` installed.
118+
Sometimes the development will have to pause so that example use case can
119+
be discussed broadly with the community. Go is a simple language, I don't want
120+
ergo to be complicated to use.
117121

118122
## Second iteration. $15k
119123

@@ -145,10 +149,14 @@ The community will be encouraged to engage with these repos.
145149

146150
A blogdown/hugo website (`https://go.rbind.io`) is in place
147151
to host blog posts related to the development, case studies, and documentation.
152+
148153
In addition, I plan to document the progress from a bird's eye view on the consortium's blog.
149154
Depending on the community's need for instant interraction, we can setup
150155
a slack team, or a gitter community.
151156

157+
A more formal scientific article in e.g. R Journal or the Journal of Statistical Software
158+
will be considered once the project is stable enough.
159+
152160
It is unclear at the time of writing this proposal if `ergo` and the packages
153161
containing `ergo` generated code can be hosted on CRAN. Both situations
154162
can be considered, but CRAN delivered packages are preferable.

0 commit comments

Comments
 (0)