Create account

2087d · Member
When is Member fully released as open-source?
1 / 11 7
1
11,000
replied 2087d
The front-end (90% of code) is already open source. Open sourcing the backend is on my roadmap - https://github.com/memberapp/memberapp.github.io/milestone/4 - however, I haven't put i
1
1,111
replied 2087d
t as a high priority as I think there are pros and cons - one of the contras i'm concerned about is that Dash and Litecoin versions will appear quickly. I'd like to see Memo and Member
1
replied 2087d
mature a little bit in the space before versions on other coins start competing. That said, I think release will need to be before/coincide with the Personal/Desktop version - https:/
1
546
replied 2086d
is this why memo is no longer open source?? I expected to hear a "memo was sold to" announcement but haven't yet... I guess this is why the main repo is gone ?
replied 2087d
/github.com/memberapp/memberapp.github.io/milestone/5

What do you think are the main pros for prioritizing releasing the back end source?
replied 2087d
Code contributions by other people
1
1,000
jarmuzceltow
replied 2085d
This could be still possible if he would document public API of his temporary closed source backend. Then anyone can extend portal but it is still copy-protected.
1
100,000
replied 2084d
https://github.com/memberapp/memberapp.github.io/issues/138
This is on my todo list. API still quite messy and changing quite rapidly atm as I add new features, so would add quite a lo
1
1
replied 2084d
t of overhead to do it before things have settled down a bit.
jarmuzceltow
replied 2083d
In such approach you have two instances of running api V1 - known publicly & frozen, second V2 without doc but used for dev and changes for the time when it becomes mature to document.
jarmuzceltow
replied 2083d
Yes,it may be an unnecessary overhead eating U time when things are changing rapidly.Best is to make snapshot & document it as v1 publicly, then do changes in v2 & documented it later.


About Privacy Terms Stats