Information and news about RFLink development and releases
Moderators: rtenklooster, Voyager, BertB, Stuntteam
-
akasma74
- New user
- Posts: 4
- Joined: 17 Apr 2018, 17:28
#11
Post
by akasma74 » 18 Apr 2018, 11:57
mrdanne wrote: ↑17 Nov 2017, 12:29
Anyone heard a solution for the Kerui sensors with R48?
nope. I emailed a debug log from one of my KERUI sensors to the developers, but haven't heard anything back.
perhaps they are still extremely busy.. :\
-
MsG
- Normal user
- Posts: 11
- Joined: 25 Jan 2017, 15:36
#12
Post
by MsG » 25 May 2018, 15:26
I get the feeling the project is becoming more and more in a hibernation mode. Too bad, because many people use it. Unfortunately the latest releases the software stopped being open source, so we can't fork it or improve it ourselves.
-
Stuntteam
- Site Beheer
- Posts: 787
- Joined: 27 Jan 2016, 16:46
#13
Post
by Stuntteam » 26 May 2018, 01:02
We are still working on it.. just not going crazy with releases.
-
Milifax
- Normal user
- Posts: 10
- Joined: 30 Jul 2017, 12:31
#14
Post
by Milifax » 21 Aug 2018, 13:15
No update for almost a year now. That's not much.
Why doesn't this project go open-source again? Wasn't it in the past?
For sure it will help development take off again.
-
Stuntteam
- Site Beheer
- Posts: 787
- Joined: 27 Jan 2016, 16:46
#15
Post
by Stuntteam » 21 Aug 2018, 14:27
Asked and answered before.. there will be updates when needed.
In the mean time we are improving and testing the code.
-
Milifax
- Normal user
- Posts: 10
- Joined: 30 Jul 2017, 12:31
#16
Post
by Milifax » 22 Aug 2018, 15:01
Stuntteam wrote: ↑21 Aug 2018, 14:27
Asked and answered before.. there will be updates when needed.
In the mean time we are improving and testing the code.
Could you direct me to the answer then? Can;t find it, maybe my bad.
What is the reason to not go open-source with this project?
-
Stuntteam
- Site Beheer
- Posts: 787
- Joined: 27 Jan 2016, 16:46
#17
Post
by Stuntteam » 22 Aug 2018, 19:59
The framework is open-source and thus available, it is all you need for plugin development.
However, the number of contributions can be counted on one hand. This obviously means there is no need for it.
The full sources are semi public, those who need it have access to it.
-
Milifax
- Normal user
- Posts: 10
- Joined: 30 Jul 2017, 12:31
#18
Post
by Milifax » 24 Aug 2018, 14:23
Stuntteam wrote: ↑22 Aug 2018, 19:59
The framework is open-source and thus available, it is all you need for plugin development.
However, the number of contributions can be counted on one hand. This obviously means there is no need for it.
The full sources are semi public, those who need it have access to it.
How can you explain this development and comments made in their post by not being able to get the latest source?
viewtopic.php?f=9&t=5730
What is the reason? I truly don't understand why one doesn't want this sw being developed in a faster pace.
Don't get me wrong, I very much like what you did (developing rflink), but I'm a big fan of open-source development as well. Just curious why these decisions are made.
-
Stuntteam
- Site Beheer
- Posts: 787
- Joined: 27 Jan 2016, 16:46
#19
Post
by Stuntteam » 24 Aug 2018, 14:38
It has nothing to do with liking or disliking open source.
Alternative versions makes development much harder for us due to unknown/unwanted changes in the code affecting timing etc.
So it is more like quality control. It is one of the reasons we put a limitation on the distribution of the source code.
The mentioned initiative is not supported by us. We are working on ESP versions and will release when they are mature enough.
The post has been wiped to avoid confusion.
-
Milifax
- Normal user
- Posts: 10
- Joined: 30 Jul 2017, 12:31
#20
Post
by Milifax » 24 Aug 2018, 16:40
Stuntteam wrote: ↑24 Aug 2018, 14:38
It has nothing to do with liking or disliking open source.
Alternative versions makes development much harder for us due to unknown/unwanted changes in the code affecting timing etc.
So it is more like quality control. It is one of the reasons we put a limitation on the distribution of the source code.
The mentioned initiative is not supported by us. We are working on ESP versions and will release when they are mature enough.
The post has been wiped to avoid confusion.
Too bad you look at it that way. So many other projects show it doesn't work like you say it would when sharing open-source (hard- and software).
Wiping the post is the worst way of dealing with new development in my opinion. Moving it to another setions maybe, but deleting it?!
However, I don't have the feeling you're open to any discussion, so we will leave it with this.
Looking forward to new releases though. Hope they will arrive soon with lots of new supported devices and improvements.
Good luck with development in the future.
-
Stuntteam
- Site Beheer
- Posts: 787
- Joined: 27 Jan 2016, 16:46
#21
Post
by Stuntteam » 28 Aug 2018, 20:37
Milifax wrote: ↑24 Aug 2018, 16:40
Wiping the post is the worst way of dealing with new development in my opinion.
Releasing under the RFlink name and posting about it in the announcements forum is in my opinion disrespectful.
If anyone wants to change my mind or tell me I am an ass then do so via PM or email.. (
frankzirrone@gmail.com)
However, we are not going to escalate this any further out here!
Who is online
Users browsing this forum: No registered users and 7 guests