Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 15 09:28
    teddlesruss opened #946
  • May 07 22:40
    sn0n commented #945
  • Apr 24 18:59
    maphew closed #881
  • Apr 04 05:35
    danielsiegl closed #767
  • Mar 09 04:47
    lavanyadeepak commented #936
  • Mar 09 04:46
    lavanyadeepak opened #945
  • Mar 09 03:55
    lavanyadeepak opened #944
  • Mar 09 03:54
    lavanyadeepak commented #940
  • Feb 22 14:54
    fon11731 commented #943
  • Feb 22 14:53
    fon11731 opened #943
  • Feb 05 07:59
    shashank-shekhar closed #120
  • Feb 04 17:59
    Anthony2k8900 commented #942
  • Feb 03 00:00
    aeonprincesca commented #942
  • Feb 02 23:59
    aeonprincesca opened #942
  • Jan 01 18:27
    CMPAssociates closed #941
  • Jan 01 18:27
    CMPAssociates commented #941
  • Jan 01 17:32
    CMPAssociates opened #941
  • Dec 04 2021 11:35
    StudyToA9 closed #940
  • Nov 26 2021 05:30
    StudyToA9 edited #940
  • Nov 26 2021 05:27
    StudyToA9 edited #940
Martin Brown
@martingbrown
I had an email from Jon a few weeks ago stating that it isn't dead and that he was going to try to get something going after he finished with Build.
Eriawan Kusumawardhono
@eriawan
aha! thanks for the heads up, @martingbrown
Eriawan Kusumawardhono
@eriawan
because this openlivewriter gitter looks dead for me...
Martin Brown
@martingbrown
I had the same thought too, hence the emails with Jon.
Eriawan Kusumawardhono
@eriawan
finished with Build? do you mean Build 2018 conference? imho, it's ended, and this repo should be alive again
it's been 8-10 days after Build ended
Martin Brown
@martingbrown
Yep 2018, that is what I was told. But be fair, Jon sounds like the only person who is actually managing this project and he does it purely as a volunteer. Lets give him a bit longer before we right it off.
Eriawan Kusumawardhono
@eriawan
fair enough. thanks for the explanation :+1:
Thomas Lee
@doctordns
it's now over a month later (who me, impatient?). I'd love to see some improvements and bugs fixed. But it appears this project has stalled (died?)
Thomas Lee
@doctordns
is this gitter page even active any more??
Sven Van den brande
@SvenVandenbrande
@doctordns Maybe, starting a new open source project could help? I also contacted @jongalloway before build. He told me, he would come with more news after build. But no new news yet. I know he is the only one that's working on the project. But he could maybe add some leads. So the project gets alive again... Other option is starting a new open source project...
Gary Ewan Park
@gep13
@SvenVandenbrande @doctordns personally, I don't think forking the project is the correct approach. OpenLiveWriter was created with the intention of being a community driven project, and I agree that this doesn't seem to have happened. What I think does need to happen is that we need to empower people (like yourselves) who are interested in helping/owning the project, and to let them run with it. That will mean handing over some control, but that is far better than letting the project dwindle.
I would love to hear @jongalloway and @shanselman and @onovotny thoughts on this from a .Net Foundation perspective.
Would there be any issues with adding more people into the OpenLiveWriter GitHub repo with the ability to commit code changes, and push out new versions?
Sven Van den brande
@SvenVandenbrande
@gep13 Forking is indeed not a good idea I think. I also think it would be better to use other technology. Now it's WinForms no? If you start with something. I would do it with a cross platform technology
And indeed it would be a good idea to empower people for this
Gary Ewan Park
@gep13
@SvenVandenbrande there are definiltey discussions to be had in this area in terms of technology choice, etc. I would say though that a lot of people like using OpenLiveWriter as it is. Yes, it might not be using the most up to date technologies, but it works, and it is good at what it done. Making wholesale chanegs to the application and it's underlying technologies would need to be done carefully. I would rather see any existing bugs in the application corrected and pushed out with new versions. This is much easier to do, and to get people up to speed with how things are done, and again empowering them to do it, and once that community base is established, further changes/improvements can be discussed, as everyone will have a better idea about what is required.
Just my two cents
I don't have any active involvement in this project, I am just an interested 3rd party :-D
Oren Novotny
@onovotny
On a plane now, but AFAIK, it's really just a matter of time / maintainers and interest
I'm sure anyone interested in stepping up would be welcome
Gary Ewan Park
@gep13
@onovotny do you know what the process for people stepping up is? Let's say @SvenVandenbrande and @doctordns were interested in doing that.
Oren Novotny
@onovotny
Let's connect over email and sort things out.
I don't monitor gitter, only noticed this because you tagged me
Gary Ewan Park
@gep13
:+1:
Thomas Lee
@doctordns
not sure I have the technical chops to do much in the way of adding code. ;-)
Sven Van den brande
@SvenVandenbrande
@gep13 I think it's all old technology. And also some difficult stuff I think.... No?
Gary Ewan Park
@gep13
@SvenVandenbrande in all honesty, I am not sure, I am not familiar with the code base. The point that I was trying to make was that I would be hesitant to jump to another technology, given that there is an existing, working, application that has a number of bugs and feature requests associated with it. There is nothing to say that anything will be any easier on a different technology stack.
Sven Van den brande
@SvenVandenbrande
@gep13 That's also true. But It would improve the user base also. :)
Sven Van den brande
@SvenVandenbrande
@onovotny I followed you on twitter. So we can exchange some contact info .... :)
Sven Van den brande
@SvenVandenbrande
And it's dead again I think. Anybody who wants to talk with me about a new project? cc: @gep13 @doctordns @onovotny
Prince Singh
@CFIAcademy
hello everyone, I am new here, and the 100th person in this room :-)
Oren Novotny
@onovotny
my email is first at last dot org.
Gareth Bradley
@garfbradaz
Hello :) Is anyone looking at the OpenLiveWriter.github.io issues? https://github.com/OpenLiveWriter/OpenLiveWriter.Github.io
Pradeep Kandel
@PradeepKandel
Hi
Can someone please help me on how to left intend in the title post bar in Open live writer?
Paperino
@aovestdipaperino
Hello, is this project still alive?
I am trying to build the installer but it's missing from the nuget package (?)
Paperino
@aovestdipaperino
(apparently you have to add squirrel's path to the PATH environment variable, which is not documented anywhere...)
Martin Brown
@martingbrown
I've been trying this as well. And I didn't have to do that. The post build project runs a batch script that has all the paths in it. It puts the installer into the releases folder. I have changed the build to work with Visual Studio 2017 though. I also had to change the version.txt file to have a higher version number otherwise squirrel fails with a file not found exception.
nikhilcartoon
@nikhilcartoon
Hello respected community,
Jim Galasyn
@JimGalasyn
Hey all, just letting you know that Open Live Writer is broken, because Google has deprecated the Picasa API. There's dismay among the Blogger community -- any chance we can get this updating with the new Google Photos Library API?
Gary Ewan Park
@gep13
As @JimGalasyn mentions, here is the GitHub issue that people can follow if interested: OpenLiveWriter/OpenLiveWriter#787
Jim Galasyn
@JimGalasyn
@gep13 The discussion has moved to here: OpenLiveWriter/OpenLiveWriter#786
Gary Ewan Park
@gep13
Yip, spotted that other issue as well. There is also some discussion about it on Twitter as well.
Jim Galasyn
@JimGalasyn
@gep13 I have a PR up that fixes this temporarily: OpenLiveWriter/OpenLiveWriter#789
Gary Ewan Park
@gep13
@JimGalasyn that is great news!
I have noticed something else that won't work during the publish, and I am trying to get the build to run on my machine, but I am running into this error:
image.png
Did you run into something similar?