Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 30 17:05

    github-actions[bot] on dev-certs

    Sign certificates (compare)

  • Jan 30 17:05

    saemy on dev-certs

    CSR for 'mariha' (compare)

  • Jan 30 17:05
    saemy closed #352
  • Jan 30 16:53
    mariha opened #352
  • Dec 20 2019 17:10

    saemy on develop

    Disable secrecy measures in tes… (compare)

  • Dec 20 2019 17:08

    saemy on develop

    Don't apply any secrecy measure… (compare)

  • Dec 18 2019 22:00

    saemy on develop

    Add support for the dev proxy s… (compare)

  • Dec 18 2019 21:54

    saemy on dev-certs

    Initial version (compare)

  • Dec 15 2019 16:50

    saemy on dispose-sub-disposable

    (compare)

  • Dec 15 2019 16:49

    saemy on develop

    wsandroid 3.1.4 (compare)

  • Dec 15 2019 16:49

    saemy on v3.1.4

    (compare)

  • Dec 15 2019 16:49

    saemy on master

    Persist user filter (#341) Rem… Fix rotation crashes (#344) * … Allow landscape for login activ… and 6 more (compare)

  • Dec 15 2019 16:32
    saemy closed #350
  • Dec 15 2019 16:32

    saemy on develop

    Use localized URL for the Warms… Propagate dispose() to nested d… (compare)

  • Dec 15 2019 16:31
    saemy synchronize #350
  • Dec 15 2019 16:31

    saemy on dispose-sub-disposable

    Use localized URL for the Warms… Propagate dispose() to nested d… (compare)

  • Dec 09 2019 00:58
    jeanfrancoisbeaulieu commented #347
  • Dec 06 2019 02:02
    isaiahmathieu opened #351
  • Dec 05 2019 06:52
    saemy review_requested #350
  • Dec 05 2019 06:52
    saemy opened #350
Kurt Ziegler
@klzig

@here I sat in on a meeting of the resurrected WS App Taskforce yesterday.

1) The plan moving forward is to require a key to access the API. While this will require rework (and totally knocks out my app, RIP), it's consistent with other API services and long overdue IMO.
2) There is now talk of addressing issues with the API. It's primarily due to 1), which in turn is due to the situation that led to disabling the API, but I'll take it.
3) We met the group that runs the web site, Skvare (https://skvare.com). Until yesterday I had no idea who these people were.
4) Tahverlee and the board are hoping to reconnect with the developers to move the apps forward. I'm afraid that if someone from this group doesn't engage with them, the current WSAndroid app will remain locked out of the API. It would be a shame (and a huge step backward for the community) to lose all of the excellent work you guys have put into this.

Allan Nordhøy
@kingu_gitlab
@klzig Why not hook the apps into TrustRoots instead. If the WS situation is what it is, beyond control of app devs, the options are to either fork the codebase or abandon ship.
sgelb
@sgelb
Everytime there are news from the board I'm fascinated by their growing incompetence. The app is dead and I think it would be a greater shame to revive it for those people who do not respect the developers or the community. It seems the board thinks that their authoritarian and intransparent leadership style is a good base for a community, so I say farewell! It was a nice time, on to new and better projects.
Thanks to all the people here with who I could work with. Open source and open communities are such powerful ideas, I hope we all meet again!
Patrick Geselbracht
@PattaFeuFeu
Farewell and thanks for your help!
Jean-François Beaulieu
@jeanfrancoisbeaulieu
Thanks @klzig for the report. Much appreciated.
Well hopefully the board comes out with a clear vision for the future of the apps. I don't think the community here would expect or appreciate anything less then that. They have mentioned going private with the app before, and if reconnecting with the developers here is just a temporary fix, I don't think it's going to be taken well.
On the other hand, if they decide to go for and support a volunteer effort for the apps for the long term, I still think it would be great. It could also be a chance to prove that it can work, and make a case for the website too. And more, with the general trend, if the apps would provide much of the functionality of the website, it would be easy to see their usage go well over the that of the website.
Although, as the exasperation of members of this community is showing, it's pretty much a last chance that is given to them, and hopefully they understand that.
Kurt Ziegler
@klzig
@kingu_gitlab I'm not familiar with TrustRoots but it looks like a great example of how community-supported development should work. Do they support externally-developed apps hooking to TrustRoots? It's not clear to me on a quick look at their site.
Allan Nordhøy
@kingu_gitlab
@klzig https://github.com/Trustroots only a webview thing, might be something in developers
Kurt Ziegler
@klzig
@jeanfrancoisbeaulieu I agree that the big question is whether the future is open community-driven development or closed. I haven't heard a definitive answer on that but signs unfortunately point to the latter. FWIW I'll make one final pitch for the former, not sure what else to do.
Kurt Ziegler
@klzig
Another possibility in the middle is that volunteer devs work collaboratively on a private repo. How do people here feel about that?
Jean-François Beaulieu
@jeanfrancoisbeaulieu
Trustroots looks great, I know of at least one former WS website volunteer that went to help there. As I remember, it used to be invite only and mostly hitchhiking, but it look like it might have changed. That been said, I like how WS as always been bike specific, and I would prefer an option that would not be trying to move the community and split it. Creating a new bike specific hosting community has been mentioned elsewhere, but I think that's really a last resort, and WS is not in a bad enough shape, yet. Yet.
Thanks @klzig for the effort and help. I'm not sure neither, I've also tried to get back in contact with Taverleh and didn't get an answer. The board seem to be in a pretty closed bubble right now, I'm also unsure of other step we could take.
As for the private/volunteer option, I can't speak for developers here, but the idea of volunteering alongside paid developers seems awkward to me. And I don't see other good reasons to why the code would be private,
Kurt Ziegler
@klzig
I agree @jeanfrancoisbeaulieu. I bring up the idea of working on a private repo because WS remains hung up on open source for reasons I don't understand and they've never articulated. I personally think such an arrangement could work if we keep/move the management and vision for the technology inside the WS org. This would allow WS to engage with paid contractors where it makes sense (maybe for the web site, I think that ship has sailed) and with volunteers where there is passion and expertise (the apps). It's clear to me that the crux of the problem is a lack of technical expertise and vision within the WS org (at the board level, where decisions are made). Until that problem is fixed I don't hold out much hope.
Jean-François Beaulieu
@jeanfrancoisbeaulieu
@klzig I see, in that way, I agree too. The recent mention of security reasons is misleading, ill-advised at best imo. Anyway, I'll let that actual developers chime in here, I'm just a designer.
Sämy
@saemy
@klzig Thank you for the summary. I'm in contact with Tahverlee, too. Although, communication is slow as I am currently out of town and response times are high on both ends...
It really makes me sad to see people like @sgelb leaving the project. Farewell, and thank you a lot for your contributions!
I am quite disagreeing with the future plans of the board, too. However, I am sticking with the project for as long as I can as I am not volunteering for the board but the community. Contrary to @jeanfrancoisbeaulieu I am not against working alongside paid developers. This is what in many other open-source projects happens, too. However, to me it is important that anyone can fork the project and develop in a direction they believe to be important. Or adding features to the official app that are high-priority for an individual while being low-priority for the board. I don't see a compelling reason for the board to not allow that. I already tried to explain to Tahverlee that security is orthogonal to that more than a month ago.
Jean-François Beaulieu
@jeanfrancoisbeaulieu
"While we help keep the apps in use, we are preparing for an RFP process to develop in-house Warmshowers apps for future use."
Oh well. Let's see what this means for the open-source status o the WS apps.
sgelb
@sgelb
In the meantime, there are now quite a lot of comments in the forum about the non-working app. Seems a lot of people do like and miss the app a lot. And, no surprise here, not a single answer from the board to clarify the situation.
And just a note for people from the forums that find their way here: the app would still work fine if the board had not decided to cut the access to the page. This was entirely their decision and not discussed with the app developers. Technically, it is a matter of minutes to reverse this and make it work again.
Sämy
@saemy
I'm happy to announce that a new, working version of wsandroid is rolling out as we speak. :tada:
Patrick Geselbracht
@PattaFeuFeu
So the API is running again?
Sämy
@saemy
Needs an API key and then yes :)
sgelb
@sgelb
Does the use of an API key interfere with the idea of an f-droid version?
Sämy
@saemy
Indeed, it does. AFAIK, F-Droid does not support to have any secrets. Everything is in the open there. But WS requires the API key to be private. So, I don't know what to do about F-Droid at the moment...
At least, the FLOSS APKs can still be downloaded from here.
noSim
@noSim

Hey, I would really like to contribute to the wsandroid project. How do I get an API key to get the build running? I planned to first start looking into whats there and maybe I than will come up with some ideas to improve or pick up an issue from the issue tracker. What would be the best way to rise those ideas? Simply open an issue?

For example one idea I had was to make profile images clickable. The one in the Sidenav to lead on your personal profile and most importantly the one in the message. Because last time I got a request I wanted to check out the profile of that person, but the only way to get to that profile was to copy paste the name into the person search. This was kinda complicated and I wished to have that feature back then :)

sgelb
@sgelb
Hey @noSim and welcome! You can propose and discuss ideas here. If you're sure your proposal makes sense, then open an issue on github. Link images to profiles for example is a good idea so go ahead.
Obviously there is an UI/UX issue here, as it is possible to long-click on a message thread and then open the user profile.
To get an API key, ask @saemy.
Sämy
@saemy
Hi @noSim. Welcome to the project!
Your ideas sound like very nice improvements. Opening new issues is always a good idea to get started. I just submitted PR #348 with some code laying around for enlarging a user profile image. Maybe you could have a look at it, what do you think? If you have any questions feel free to ask here.
noSim
@noSim
@saemy this looks like a good task to get into the project. I will have a look.
Jean-François Beaulieu
@jeanfrancoisbeaulieu
If you submit an issue or PR I can comment there, but one another idea is to have a vertical elipsis menu in the chat window with 'show profile' or something like that.
noSim
@noSim
@jeanfrancoisbeaulieu despite I would consider clicking the profile image is more a hidden "power user" feature, I like your idea as well and would maybe even go with both options. Also because clicking the image is only possible in the overview. But I would prefer to simply put a profile icon in the top right corner instead of an elipsis menu. I would go for the elipsis menu only if you have 3+ items.
I will open an issue as soon as I get started and have looked a little bit into the code base.
Jean-François Beaulieu
@jeanfrancoisbeaulieu
Sounds like that would be good too. Let me know when you have the issue opened.
noSim
@noSim
Hey, I still have no API key, but I already looked into the code base. I also had an idea to improve the sidenav profile picture. Currently it is always loading the small image, but if Wifi is present or it is already cached, the large image could be loaded. I also uploaded a commit on my fork implementing this behavior ( noSim/wsandroid@1652537 ). But by now I could not test it, since I have no API key to build against the API. Is it okay if I open a pull request despite, no testing yet from my side? ( I might also add a test to check my code)
Sämy
@saemy
You can just open a PR, yes.
Isaiah Mathieu
@isaiahmathieu
Hello, I would like to contribute to the project. Can someone send me an api user id and api key so that I can build the projects? thank you.
Sämy
@saemy
Hi @isaiahmathieu. Welcome to the project!
I'll look into getting you a key. I cannot issue them but am going to reach out to the board. Please, PM me your Warmshowers userId? (It is the number in the url of your profile page on warmshowers.org). It might take a while to get your key.
Do you already have some ideas what you would like to work on? :)
Isaiah Mathieu
@isaiahmathieu
ok i'll send a PM. I just want to work on bug fixes for now and other small improvements. I was hosted by warm showers hosts a lot this past summer so I want to give back to the community.
thanks!
sgelb
@sgelb
Anyone heard about the Request For Proposals (RFP) for the development of an Android and iOS app? https://www.warmshowers.org/node/348729
Interesting document. The next app will not be free, and there are some requirements which would also need changes on the backend. The application was open for just 10 days and closed yesterday. That is not a lot of time, especially right before Christmas.
This message was deleted
Jean-François Beaulieu
@jeanfrancoisbeaulieu
I haven't heard about this, but it is pretty significant. Pretty much seals it for me for WS. Sad to hear.
Mariha Kozinska
@mariha
Hi guys,
Mariha Kozinska
@mariha
I am new here, I’ve found this chat while I was researching for WS in last days. Me and my husband Szymon are members of the WS community for a few years. We are also professional software engineers (Szymon - Android, me - backend java).
About 3 years ago we offered our help in improving the app as volunteers, didn’t get any response though.
Mariha Kozinska
@mariha
A month ago I happened to read the newsletter to the very end and see the request for proposal. We drafted a design and answered to the REP, offering to develop and maintain the apps and new server side pro publicity bono. We also mentioned that it would be great to run it as an open source project as we are sure other members of the community are willing to help.
So far didn’t get an answer though, so was thinking if you know anything what’s happening?
I am freaked out by the fact that such an enormous community may stop existing because of some dumb technical issues.
Sämy
@saemy

Hi @mariha, welcome to the WSAndroid chat.
Where should I start..? Well, great that you applied for the RFP and even greater that you are willing to provide a solution that keeps the apps open source! We - the volunteers that maintain the android app - are obviously in favor of that path forward. In fact, we advised the board many times in the past to keep their source open - even if they decide to work together with paid software developers that ensure that progress is made, bugs are fixed, ... Personally, I'd be very happy to see an applicant like you getting the concession.
Unfortunately, the communication of the board has always been quite sparse and turned to almost non-existing in the past years. Therefore, I was not surprised to find a topic as important as the late request for proposal at the very end of a newsletter convoluted with another donation success story. So no, I unfortunately don't know anything about the progress of the RFP - the last I heard from the board was a notice one day before they sent out the newsletter to everyone. I suggest that you directly ask them about the progress (and maybe keep us posted? :wink:)

All of that said, the current wsandroid project is not dead (yet). And I guess it won't be until mid to end of this year. There are still cyclists on the road and we are still happy to provide the community with a nice and working app. So 3 years after your initial offer for help: Yes, we are in need of volunteers and would be very happy to welcome you aboard. Look at the readme on the Github page for how to get a developer certificate and how to build the app. Then we can chat here about any bugs/features you want to work on. If you need help I am here to help you. Thank you.

Mariha Kozinska
@mariha
just fyi, I haven't heard from the board/tech committee anything so far. A month after applying for the RFP I got a message from Tahverlee that she is moving the conversation to her account, a few days later I followed up asking for updates, I am still waiting for the answer...