allura-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/2] allura-site git commit: Fix Two-Factor link
Date Fri, 16 Dec 2016 19:32:17 GMT
Repository: allura-site
Updated Branches:
  refs/heads/asf-site d6f23fc4f -> 503c44972
diff --git a/posts/2016-gsoc-16.html b/posts/2016-gsoc-16.html
index 0a07a50..9c709d3 100644
--- a/posts/2016-gsoc-16.html
+++ b/posts/2016-gsoc-16.html
@@ -73,33 +73,33 @@
 <h3>Discussion Tool Changes</h3>
 <p>The idea behind this change was to promote discussions on the platform. Most conversations
on the web are now displayed in a similar format. The replies to a comment are also now anchored
to the left, i.e. don't become shorter in length and are only shifted towards the left along
with a smaller avatar. We have also moved away from shadows under the avatars since they do
not match with the current design scheme.</p>
 <p>The design enhances the username and avatar of the user to make it easier to recognize
who has authored the comment. Also, the buttons used to interact in the discussion are now
displayed on the upper right side. Also, there is now a unified design theme for all buttons
including the moderation buttons. These set of buttons can easily be extendened in the future
as well. This also makes more space available for the content. Images now do not overflow
outside these bubbles and fit inside the bubbles.</p>
-<p><img alt="Design Example of Discussion" src=""
+<p><img alt="Design Example of Discussion" src=""></p>
 <p>Another prominent change is how we now display attachments. There is now a dedicated
download and delete button for all attachments and an icon beside the file name displaying
the type of attachment.</p>
 <p>Support for viewing the photo attachments has also been added by clicking on the
image thumbnail inside the attachment box.</p>
-<p><img alt="Preview Images" src="" /></p>
+<p><img alt="Preview Images" src=""></p>
 <p>There has also been a change in how we display meta posts which share information
rather than conversational text that is generated by the interaction of the user with the
tools. These are not highlighted and uses smaller fonts so it is easier for the eyes to find
real content and also distinguish between meta information and the same.</p>
-<p><img alt="Meta Posts" src="" /></p>
+<p><img alt="Meta Posts" src=""></p>
 <p>You can also use Unicode Emoji's within the discussion tool and they will be rendered
as Twitter Style Emoji. This is very useful since we now have support for displaying the emoji
even if the user don't have the proper font's to render them in his browser. </p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>Emoji Support enables users to use their devices emoji input keyboards and enter
data. Also, now teams can use a simple Thumbs Up emoji instead of writing words to express
 <p>You can view the results live on <a href="">SourceForge</a>
as well.</p>
 <h3>Improved Landing Page</h3>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>We now have a better landing page. A landing page is forms the first impression
for the tool. Although, if you are probably using SourceForge, your landing page might be
the Project Catalog. </p>
 <p>Now we list all the neighborhoods in a block showing it's logo along with the name
and number of projects it contains. </p>
 <p>It makes it easier to digest the concept of neighborhoods for users who are used
to something similar to Github or GitLab.</p>
 <h3>Minor Improvements in Ticket Listing and Search</h3>
 <p>Now you can resize the length of the columns in the ticket listing.</p>
-<p><img alt="Resize" src="" /></p>
+<p><img alt="Resize" src=""></p>
 <p>Also you can now click on the username in the Owner column to view all tickets that
have been assigned to that user directly from the ticket listing.</p>
 <h3>Merge Request Flow Improvements</h3>
 <p>Now we show a link to Merge Requests listing in the side panel in all tools that
support them even if none have been created. </p>
-<p><img alt="List if zero" src="" /></p>
+<p><img alt="List if zero" src=""></p>
 <p>Also the filtering of merge requests have changed a bit. Now we have a new set of
filter buttons that we use to filter the merge requests that are either open, rejected, merged.
-<p><img alt="Filter MRs" src="" /></p>
+<p><img alt="Filter MRs" src=""></p>
 <p>Also, there are now dedicated buttons matching the Forge theme that you can use
to manage your merge requests. We now have an array of buttons and a text message that displays
the status of the merge conflicts and if a one click merge is possible if you have access
to that information. Users with correct priveleges can also click on the Reject button to
reject and close the MR in two clicks including a confirmation dialog. </p>
 <p>Also, you can now Refresh the commits without having to manually edit the merge
request, saving 4-5 clicks using the Refresh Commits button.</p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <h3>What could not be completed or was not done</h3>
 <h4>Implement async loading of comments and allow them to be paginated.</h4>
 <p>This was not implemented since there would be a loss in the traffic for the discussions.
This would have a huge impact in search rankings for comments since crawlers don't index async
loaded comments and searching for problems on the internet is a very important way to reach
this content. Suppose you have a problem you have faced with TexStudio software and search
about it on a search engine and someone else has also reported a problem on it's bug tracker
then if it is not indexed in the search engine we will not be able to find it on the search
@@ -113,9 +113,9 @@
 <h4>Extend the models in the threads to allow voting(express +1, LGTM etc.) on individual
 <p>There were two ways I tried to implement this. </p>
 <p>First was to add a thumbs up button on the menu of the discussion bubble along side
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>Clicking that button adds a meta post as a reply to the post. But it looks ugly
and does not seem useful.</p>
-<p><img alt="Plus 1" src="" /></p>
+<p><img alt="Plus 1" src=""></p>
 <p>The other method was to try to make the artifact votable but here the problem was
that I could not get it to work as per my thought of how it should look and work. In this
way I wanted a menu on the bottom. </p>
 <p>The code for all of these unimplemented work is available on my forked repo on forge-allura
<a href="">here</a>.
You can find all the branches with the unimplemented work mentioned here as well as other
experiments. (My Branches begin with <code>feature</code> or <code>rhnvrm/</code>)</p>
 <h3>Other Cool Stuff I did related to Allura</h3>
@@ -134,7 +134,7 @@ clone the repository using <code>git clone https://rhnvrm@forge-allura.apache.or
 <p>To show how it can even be run on a low powered device I installed Allura for me
and my friends on a RPi 3B model.</p>
 <p>There were various problems that I faced during installation due to it being an
ARM based device. I first tried to install using docker since it was easier but after installing
docker and docker-compose from hyperiot I soon realized that it was not possible as it is
ARM based and we don't provide docker support for that.</p>
 <p>Here the makefile was very useful. Although I did not use it directly but I atleast
had an idea how to install Allura step by step instead of having to re read the manual again
and again.</p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <h4>Deployed Allura for my University</h4>
 <p>Using the Raspberry Pi I am planning to deploy it for my university for using it
for our Coding Club and also for internal usage. I have emailed my department and am hoping
for a positive response.</p>
 <h4>Setup and hosted a small Allura Instance for testing on Digital Ocean</h4>
diff --git a/posts/2016-two-factor-auth.html b/posts/2016-two-factor-auth.html
index 74c32f9..e5b660c 100644
--- a/posts/2016-two-factor-auth.html
+++ b/posts/2016-two-factor-auth.html
@@ -70,18 +70,18 @@
       <div class="row">
         <div class="pad-md text-black"><p>Support for enabling Two Factor Authentication(2FA)
for users is now available in Allura's master branch. </p>
 <p>Users can enable 2FA by visiting their account preferences page and set it up.</p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>After clicking on the setup page, users will be asked for their password. </p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>Users then install the Google Authenticator App for their smartphones. The links
to install it can also be emailed to their accounts so that the link can be accessed from
their phone. </p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>Users then scan the barcode and enter the time based six digit one time password
generated by the mobile app in Allura. </p>
 <p>After successfully setting up 2FA, users will be provided with recovery codes which
can be used incase users get locked out of their account.</p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>An email is also sent to the user. </p>
-<p><img alt="Imgur" src="" /></p>
+<p><img alt="Imgur" src=""></p>
 <p>Users can also modify their settings and view the recovery codes as well as disable
2FA from their account preferences.</p>
-<p><img alt="Imgur" src="" /></p></div>
+<p><img alt="Imgur" src=""></p></div>

View raw message