fireside chat 3

posts/_posts/2016-09-29-fireside-chat-3-we-can-rebuild-it-we-have-the-technology.md

@@ -1,6 +1,6 @@
 ---
 title: '[Fireside Chat #3] We can rebuild it, we have the technology'
-author: David Sparer
+author: dmsparer
 tags: fireside
 ---
 
@@ -8,7 +8,7 @@ Hello mRemoteNG users!
 
 Here is another extrememly overdue update from the dev team.
 
-We've been hard at work getting v1.75 ready for alpha/beta testing. I think we are getting close(r) This update was slated to be security-focused with many important improvements. While that's still mostly the case, it has been diluted a bit. When we took a look at the areas of the program that we wanted to change over the next few versions, it became clear that the architecture of the application was going to be a significant burden. Much of the code was tightly woven with how things get displayed and how that display should react when data changes.
+We've been hard at work getting v1.75 ready for alpha/beta testing. I think we are getting close(r). This update was slated to be security-focused with many important improvements. While that's still mostly the case, it has been diluted a bit. When we took a look at the areas of the program that we wanted to change over the next few versions, it became clear that the architecture of the application was going to be a significant burden. Much of the code was tightly woven with how things get displayed and how that display should react when data changes.
 
 #### What has happened:
 * Large re-write of anything that touched the TreeView displayed. If it dared to talk about TreeNodes, it was rewriten. Unfortunately, this took up most of the last month.
@@ -19,7 +19,7 @@ We've been hard at work getting v1.75 ready for alpha/beta testing. I think we a
 * On the plus side, the new encryption algorithms (using BouncyCastle) are in place on the develop branch. These are not yet used within the application, though thats the next focus after the re-write mentioned above is finished. There will be a forced upgrade of the encryption used on connections files. If you are encrypting your confCons (you should), there will be a one-time upgrade to use the newer encryption. There will be several options, with AES-GCM being the default. We need folks to check the implementation - if you find any flaws please let us know immediately.
 * We've added a bunch of new unit/integration tests. We aren't even close to having the whole project covered, but we've got a start.
 * Bennett Blodinger has built out a new website powered by GitHub Pages (thanks Bennett!). In the coming weeks we will re-point the mremoteng.org domain to this new site. You can view the new mock-up here: [https://mremoteng.github.io/mRemoteNG/](https://mremoteng.github.io/mRemoteNG/)
-* We have also decided to eventually move all of our bug/feature/improvement tracking from Jira to GitHub Issues. We currently do not have a timeline for switching over. There are a couple of reasons that we decided to make the switch:
+* We are moving all bug/request tracking from Jira to GitHub Issues. Please create new bug/request tickets here: [https://github.com/mRemoteNG/mRemoteNG/issues](https://github.com/mRemoteNG/mRemoteNG/issues). We will still accept Jira tickets for the time being, though the ability to create new tickets will be turned off sometime soon-ish. After that, we will migrate existing tickets from Jira to GitHub. There are a couple of reasons that we decided to make the switch:
   * Jira is one more account/system between you and getting your issue addressed.
   * GitHub Issues will integrate better with our other solutions (chat/Jenkins/website).
   * GitHub Issues will be more visible to the community (because of the previous two reasons).