This repository has been archived by the owner on Jan 26, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 209
GSoC 2014 Shwetambara Srivastava, Ana Balica, Chitra Khatwani
Janice Niemeir edited this page Jan 25, 2018
·
1 revision
Shwetambara Srivastava
Ana Balica
Chitra Khatwani
I am a Final year undergraduate pursuing Bachelor of Technology in Computer Science and Engineering from India. I love to Code and this is my first Open Source Experience.
Github
Twitter
LinkedIn
Email-Id
I'll be working on the project of Testing Automation for Systers Portal. My work will basically focus on creating a testing Framework for the web app of portal using Java as the language and Selenium(JUnit) for the framework ad Maven as the Build tool. I'll be starting with setting up the testing environment and then creating unit tests and later integrating these to finally build regression testing suites.
Features yet to be discussed in detail with mentors and teams.
Here is a Link to my project proposal. Feel free to scroll down to the initial timeline proposed
This will however change according to the progress made on the project.
To be added later.
To be added later.
- Going through various documentations available on Selenium, Junit framework, UI testing
- Setting Up the VM
- Trying simple Selenium scripts like “hello world”
- Tried to install CentOS based VM which was previous used by Systers which did not have many useful packages preinstalled in it. I was new to the CentOS environment
- Also was not familiar with Vagrant to begin with
- We now have a newer VM on Ubuntu which sports many Software packages already installed so now need to download them individually
- I also read documentations on Vagrant and now I am familiar to its working
- Still need Testing Specific Softwares on the VM so can begin with the testing on VM itself
- The required softwares are due to be installed soon
- Will try to set up selenium server on VM
- Read more about JUnit and Selenium
- Writing basic test scripts
- Gather Information about the Requirements of Portal team and prepare an elaborate design
- Try Maven and learn about it
- Accomplished almost all the tasks schedule for this week, except setting up the selenium server on VM
- This is my week#1 report on Systers wiki
- learning more about Selenium along with JUnit
- Trying simple Selenium scripts in Java/JUnit/Webdriver format instead of selenese
- Installed X Windows for the VM from systers-autotest folder
- Tried to install the X windows but apparently I'm getting some V_BOX error which I will have troubleshoot and see if I can fix it.
- System memory full
- User login on systers-dev wiki failed to recognize my account and couldn't find any "register" option to make another account.
- System memory has been restored to optimal size by clearing out some files that were eating space
- The issues concerning Login page still persists.
- I am working on the troubleshooting for X-windows installation
- Dorota informed Rose about the login issue
- The login page issue will be resolved by the Oregon State University Open Source Lab in a couple of days
- I shall be working on creating login tests making use of selenium and JUnit
- Learn more about Ant, I will also explore the use of Ant in my test automation
- Did all the tasks listed in the last weekly report for tasks for the week except selenium server setting in my VM
- I will also be making a switch to learn Ant instead of Ant as Ant appears to be more Java friendly build tool.
- Still have to successfully accomplish the task of X-Windows proper installation, though that being just for GUI and so I can continue with the terminal in the meanwhile
- Made Login tests for the login page of Systers that includes a positve test and a negative test
- Pushed the code on Github repository
- Made an account on podio.com and shared my milestones with the other members of testing automation team
- Tried to install the X windows but apparently I'm getting some V_BOX error which I will have troubleshoot and see if I can fix it.
- System memory full Have they been resolved, and if so, how?
- Not yet, they keep cropping up after a while.
- Discussed this memory issue with my mentor
- Looking for a permanent solution for this
- I'll have to work on the issues myself
- I shall be working on creating login tests considering different user accounts on the page.
- Create a dummy page imitating the structure of Systers-dev wiki and make dummy users on it for the login tests and authentication
- Learn more about Ant, I will also explore the use of Ant in my test automation
- The progress is happening at a slow pace than anticipated due to the initial setting up on the project, which I hope to compensate in the upcoming fortnight.
- Made more UI tests scripts on the login page of Systers-dev
- Pushed the code on Github repository which can be seen here
- The login page doesn't permit for random user registration so could not yet prepare test scripts for after successful login cases.
N/A
Do not have the permission to create user account at random
Will have to create a dummy page imitating the structure of Systers-dev wiki and make dummy users on it for the login tests and authentication.
- Integrate Ant with JUnit framework and run the test cases from the build file
- Create more test cases over the next few days
The progress is slightly lagging which will hopefully be covered in a couple of days
- Made more UI tests scripts on the login page of Systers-dev
- Modified the code for previous tests on Github repository which can be seen here
- Working on the Ant build file for running the JUnit test cases
- Facing issues with Ant. Not yet able to get the file to run successfully
- Resolved some of the issues. Tried setting the classpath to more absolute address for the .jar files. Also added the external JAR files to the project, which removed the compile time errors previously present.
- Have to attach source for few .jar files counter the runtime errors.
- I request guidance from my mentor whenever in doubt.
- Integrate Ant with JUnit framework and run the test cases from the build file
- Create JUnit parameterized tests for more flexible test cases
- Right on track
- Made parameterized test cases to provide more variability in the input for the testing
- None so far
- N/A
- N/A
- N/A
- I have a meeting with the development team to discuss status of the project, where we shall chalk out the schedule for next few days and also understand the prerequisites for the testing of Portal
- Create more parameterized testcases and push it on github
- Setup the environment to facilitate cloning and hosting of the project on my machine for UI testing.
- Start working on the testing of dashboard models
- Right on track
- Made parameterized test cases to provide more variability in the input for the testing. The code can be seen at
- Did a Google+ Hangout meeting with the development team on 2nd July regarding their work progress and more detailed discussion on testing of the Systers Portal.
- Reading their requirement and prerequisites and understanding the working of Django framework that is used for Portal development.
- None so far
- N/A
- N/A
- N/A
- Setup the environment to facilitate cloning and hosting of the project on my machine for UI testing.
- Start working on the testing of dashboard models
- Behind the schedule
- Working on writing tests for checking queries for database by making a dummy database and assuming the needed variables.
- Did a Google+ Hangout meeting with my mentor, discussing our timeline and the tasks to be done in the next few days.
- Slow Internet connectivity lead to delay in communication this week
- Could not clone and host the code for Portal as was expected as in this week due to the pending pull requests
- Yes
- N/A
- Will be keeping in touch with the Development team for the help in setting up the environment
- Setup the environment to facilitate cloning and hosting of the project on my machine for UI testing.
- Start working on the testing of dashboard models
- Push code for DB testing in a couple of days
- Behind the schedule
- Working on writing tests for checking queries for database by making a dummy database and assuming the needed variables.
- Pushed some initial basic code of the above on the fork of systers-automated repository, yet to be reviewed by mentor.
- Setting up the environment to host Portal code on my machine
- Did a Google+ Hangout meeting with my mentor, discussing our timeline and the tasks to be done in the next few days.
- Slow Internet connectivity lead to delay in communication this week
- Yes
- N/A
- N/A
- Finish the Setup of environment to facilitate cloning and hosting of the project on my machine for UI testing.
- Have a code review with mentor and discuss questions regarding the same
- Behind the schedule
- Did the setup for hosting of Systers Portal on my local machine
- Made few UI testcases for the Portal
- Discussed more testcases Ideas with mentor, presently working on them
- It took a lot of time to be able to configure the development server on my machine for the portal hosting due to some unknown compatibility issues with my machine
- Yes, Had to perform all the installations individually using pip
- N/A
- It would be simpler and more efficient if we can host the Portal on test server of Systers for future reference rather than doing it on local machines.
- Write more testcases for the Portal and push them on github automated testing repository
- Make documentations on the wiki for codes written and the setting up manual
- Behind schedule
- Made UI testcases for the Portal and pushed few of them on github here
- Started documenting on wiki and automated-testing repository
- The login feature of the portal was facing several bugs and is in developmental stage and so new functionalities keep on getting incremented. Had to discard few of the previous feature dependent test cases that are no longer relevant.
- N/A
- Now making a more generic test suite for the java test framework
- N/A
- Write more testcases for the Portal and push them on github automated testing repository. And also refine the already existing ones
- Update previous Database related test cases
- Make documentations on the wiki for codes written and the setting up manual
- Behind schedule
- Made UI testcases for the Portal and pushed few of them on github []here](https://github.com/systers/automated-testing/tree/master/PortalTests)
- Started documenting on wiki and automated-testing repository
- The login feature of the portal was facing several bugs and is in developmental stage and so new functionalities keep on getting incremented. Had to discard few of the previous feature dependent test cases that are no longer relevant.
- N/A
- Now making a more generic test suite for the java test framework
- N/A
- Write more testcases for the Portal and push them on github automated testing repository. And also refine the already existing ones
- Update previous Database related test cases
- Make documentations on the wiki for codes written and the setting up manual
- Behind schedule
Student, coder, traveller.
Website
Github
Bitbucket
Twitter
LinkedIn
This summer together with Chitra Khatwani I will be working on Systers Portal - a place for Systers communities and sub-communities to share information.
| Period of time | Assignee | Tasks |
|---|---|---|
| 19 - 25 May | Chitra | 1) Initial setup and configuration of Django project |
| 2) Create User, Organization, Community models | ||
| Ana | 1) Setup and configure buildbot | |
| 2) Create login page with authentication (standalone login and django-social-auth) | ||
| 26 - 1 June | Chitra | 1) Create registration, password reset functionality |
| 2) Create password change functionality | ||
| Ana | 1) Configure django admin default app and add a custom skin | |
| 2) Extend django admin app to create dynamic group permissions | ||
| 1 June | Project major milestone: Fully functional register/login mechanism | |
| 9 - 15 June | Chitra | 1) Create SuperAdmin Dashboard (only the dashboard, don’t include all the subfunctionalities) |
| 2) User profile edit | ||
| Ana | 1) Implement organization profile form functionality, allow edit for SuperAdmin only | |
| 2) Implement community profile form functionality, allow edit according to the user permissions | ||
| 16 - 29 June | Chitra | Implement create new community process - new community, community profile, community resource area |
| Ana | Manage users page - extend django admin app to allow assigning access level to users | |
| 27 June | Mid-term evaluation | |
| 1 June | Project major milestone: Levels of access implemented. Raw admin dashboard. Organization, community and user profiles | |
| 30 - 6 July | Chitra | 1) Request creation of a new community form |
| 2) Process new community requests functionality | ||
| Ana | 1) Edit community profile | |
| 2) Add, edit, delete news, resources functionality | ||
| 7 - 13 July | Chitra | Page with a list of all communities available from admin dashboard |
| Ana | Process of new community requests functionality (accept, reject, send feedback) | |
| 14-20 July | Chitra | Social media integration |
| Ana | Integration with meetup.com API | |
| 21 - 27 July | Chitra | Add comments section |
| Ana | Implement set up of public/private pages | |
| 27 July | Project major milestone: Full admin dashboard. Community creation functionality. Manipulation of communities’ resource area. Social media integration. | |
| 28 - 3 August | Chitra, Ana | Refactor code segments if necessary, clean code, solve unexpected issues, bugfixes |
| 4 - 10 August | Chitra, Ana | Write documentation, provide contribution guidelines, create a deployment script |
| 11 - 22 August | Chitra, Ana | Polishing of code, submitting code to melange |
| 22 August | Final evaluation |
The requirements of Systers Portal project are in the github repo.
More details and a basic FAQ can be found here.
Mockups of Systers Portal are hosted here.
- Went through requirements very carefully, broke them down into task and pages, clarified the ambiguous requirements
- Created UI mockups with Chitra
- Updated the timeline with a merged version of mine and Chitra's
- Decided on Django models and their fields that will be used in PTL
- Looked at the meetup API, which can be used into PTL
- Tested the Peace Corps VM
- The only blocker represents the VM.
- Not yet, but it's a matter of time.
- N/A
- N/A
- Install and configure buildbot, python PEP8 checker
- Create login page with authentication (stand-alone and django-social-auth)
- Configure django admin app to and add a custom skin
- Behind.
- Pulled and ran Portal VM locally
- Setup flake8 Python lint
- Start working on stand-alone registration
- Updated the Sphinx PR
- The usage of third-party libraries.
- Yes. Before using any, we should pay attention how popular and maintained are those.
- No
- No
- Try django project inside VM
- Configure outbound email via SMTP
- Finish stand-alone registration
- Create login page
- Behind.
- Listed all the tasks and subtasks in Asana, set deadlines and assignee
- Ran sample portal project in VM and configured the local environment for development
- Configured SMTP mail sending in Django
- Configured django-allauth which has the following functionality:
- local signup with email confirmation
- sign in / logout
- password change
- password reset
- sign in using social accounts
- Tested social signin using Google OAuth2
- Implemented the creation and saving of custom user model on user signup with auth app
- Enabled django-admin app and added custom "grappelli" skin to django-admin
- Went through buildbot documentation
- Pending model reviews.
- I have created a dummy model for testing the custom user model save on signup. It works as a proof of concept and the existing code can be easily used with the updated custom user models.
- Somehow yes, but tomorrow we get in touch with mentors and can solve many of the issues.
- Yes.
- Add unittests to the "create custom user model on signup" functionality
- Create PRs, update and fix according to the mentors' suggestions
- Work on dynamic group permissions
- Behind, thought we speed up.
- Ran buildbot on my local machine
- Updated the pull request with django-start-project
- Configured py.test for the portal project
- Did a codereview
- None
- N/A
- N/A
- N/A
- PR allauth branch after having start-project branch merged
- Configure Travis CI for portal project
- Create custom dynamic permissions with django-authority
- Behind. This is the week before the thesis presentation and had a lot of work to do. I will catch up this week
- Configure Travis CI and test on my fork, PR accepted
- Finished Django start project with configuration of django-nose, flake8, PR accepted
- Updated allauth branch and wrote a unittest for creation of SysterUser on auth user signup
- Enabled and configured admin app and skin (PR ready, but not sent yet, since on automatic merge it will conflict with the previous pending PR)
- Read django-authority documentation and created some sample custom permissions with it
- Still pending models (using dummy models for permissions)
- Nope
- Yes. Did a codereview on models, suggested some improvements, gave some tips on git history rewriting and syncing a fork.
- Yes.
- Get allauth and admin-app PRs accepted (with suggested improvements)
- Create dynamic permissions and establish groups
- Create organization profile functionality + unittests
- Behind.
- Fixed the issue with travis-ci secure env variables and added a status build button to README.md
- Created user groups and assigned permissions to each group
- Unittesting of user groups.
- Yes, Lynn proposed to place the post db sync code inside
systers_postal/management/__ini__.py, which made the trick
- No
- No
- Create decorators for checking if a user is member of a specific community and if user is a community admin
- Create organization profile functionality + unittests
- Behind.
- Added view decorators to check user membership, authorship and admin rights; added doctests and unittests to decorators
- Created Community page view and template, Community form with form unittests
- Updated testing settings for running doctests
- Separate requirements files for production and testing
- Started the discussion and proposed a consistent URL schema
- Started writing documentation for social apps configuration
- Unittesting views by using the django client. In test mode it can't import the urls (
ImportError: No module named urls).
- No
- Yes. Changing url patters and ROOT_URLCONF, reading through django documentation and stackoverflow.
- Yes
- Finish with social apps documentation
- Write unittests for community views
- Create manage users functionality
- Behind.
- Finished social apps documentation
- Displaying public community profile functionality
- Editing community profile functionality
- None
- N/A
- N/A
- N/A
- Manage users functionality
- Row/object level permissions
- Management of community resource area
- Behind.
- Update editing of community profile
- Create object level permissions groups for Community objects with django-guardian
- Create group with generic permissions
- Hook post_save signal to perform different actions: set community admin as member of Community Admin group, grant access to parent community admins for child community, give basic permissions to users of other groups.
- None
- N/A
- N/A
- N/A
- Manage users functionality
- Create a demo branch
- Deploy portal on test server
- Behind.
- Created a demo branch by merging all the existing functionality - unittests and flake8 linter pass all tests, though didn't test manually
- Created view/template with a table of community users
- Deployed master branch on heroku (on this branch there is no index page, hence 404)
- Deployed demo branch on heroku
- Getting sudo access on test server for deployment using apache. I am able to restart the apache without sudo (my user has access to that), but still can't execute commands with sudo - prompts for a password.
- I pinged Rajesh directly on GTalk to ask him if I am doing something wrong.
- Probably the message is hidden. Will send an email.
- Yes. Meanwhile I have decided to deploy our project on heroku - took me 2 days of tackling with settings, but finally it works.
- Yes
- Add/Change/delete user permissions
- Create master and demo scenarios for demo day, test manually and fix everything on demo branch
- Deploy the documentation (including API) on readthedocs
- Behind.
- Made some UI fixes for the demo
- Ran the demo with Rose
- Add/Change/Delete user permissions
- Created master and demo scenarios for demo day
- Deployed the documentation on readthedocs
- None
- N/A
- N/A
- N/A
- New community request functionality
- Use fixtures to enter initial database data
- Fix bugs (500 on user register, facebook auth, etc)
- Behind.
- New community request functionality
- Bugfixing (on login, register, social login)
- New UI - main page, sign in, register, user profile, community main page
- None
- N/A
- N/A
- N/A
- Bugfixing
- UI improvements
- Documentation
- OK.
I am undergraduate student at International Institute of Information Technology Hyderabad, India. I strive to be open to all learning opportunities. My areas of interest include coding, algorithms, software development.
Webpage
Github
Twitter
LinkedIn
I will be working on Systers Portal Project with Ana Balica. The project aims at building a portal for Systers and sub-groups to share information to perspective communities, lists events and by geography.
to be listed later
| Period of time | Assignee | Tasks |
|---|---|---|
| 19 - 25 May | Chitra | 1) Initial setup and configuration of Django project |
| 2) Create User, Organization, Community models | ||
| Ana | 1) Setup and configure buildbot | |
| 2) Create login page with authentication (standalone login and django-social-auth) | ||
| 26 - 1 June | Chitra | 1) Create registration, password reset functionality |
| 2) Create password change functionality | ||
| Ana | 1) Configure django admin default app and add a custom skin | |
| 2) Extend django admin app to create dynamic group permissions | ||
| 1 June | Project major milestone: Fully functional register/login mechanism | |
| 9 - 15 June | Chitra | 1) Create SuperAdmin Dashboard (only the dashboard, don’t include all the subfunctionalities) |
| 2) User profile edit | ||
| Ana | 1) Implement organization profile form functionality, allow edit for SuperAdmin only | |
| 2) Implement community profile form functionality, allow edit according to the user permissions | ||
| 16 - 29 June | Chitra | Implement create new community process - new community, community profile, community resource area |
| Ana | Manage users page - extend django admin app to allow assigning access level to users | |
| 27 June | Mid-term evaluation | |
| 1 June | Project major milestone: Levels of access implemented. Raw admin dashboard. Organization, community and user profiles | |
| 30 - 6 July | Chitra | 1) Edit community profile |
| 2) Add, edit, delete news, resources functionality | ||
| Ana | 1) Request creation of a new community form | |
| 2) Process new community requests functionality | ||
| 7 - 13 July | Chitra | Page with a list of all communities available from admin dashboard |
| Ana | Process of new community requests functionality (accept, reject, send feedback) | |
| 14-20 July | Chitra | Social media integration |
| Ana | Integration with meetup.com API | |
| 21 - 27 July | Chitra | Add comments section |
| Ana | Implement set up of public/private pages | |
| 27 July | Project major milestone: Full admin dashboard. Community creation functionality. Manipulation of communities’ resource area. Social media integration. | |
| 28 - 3 August | Chitra, Ana | Refactor code segments if necessary, clean code, solve unexpected issues, bugfixes |
| 4 - 10 August | Chitra, Ana | Write documentation, provide contribution guidelines, create a deployment script |
| 11 - 22 August | Chitra, Ana | Polishing of code, submitting code to melange |
| 22 August | Final evaluation |
The requirements of Systers Portal project are in the github repo.
More details and a basic FAQ can be found here.
Mockups of Systers Portal are hosted here.
To be listed later
- This week I started with the design of Systers Portal. We have some mockups of systers portal which are hosted here
- The below specific mockups are designed by me :
- General user profile
- Change password
- Super Administrator Dashboard
- Organization (Systers) profile
- Community (LGBT, ArabWiC etc) profile
- Create new community by the SuperAdmin
- Create Meetups
- Community Admin Dashboard
- Decided upon the models and their fields that we will be having for systers portal
- Discussion about models can be found here
- Went through the requirements carefully and cleared the ambiguous requirements after discussions with Ana Balica and Rose. After detailed discussions on requirements with my team mate Ana Balica and Rose Robinson
- Came up with the following tasks for Systers Portal. Tasks can be found here
- Came up with a new timeline after discussing with Ana.
- Tested the Peace Corps VM
- The only blocker represents the VM, that has not yet been set up for our project.
- As such there were no roadblocks
- We were not clear with some requirements and so we had some questions which we cleared by holding a meeting with Rose.
- All the questions can be found here
- Not yet.
- N/A.
- N/A
- Initial Setup and Configuration of django project
- User register and Login functionality.
- Our development environment has not been set up yet , so we are behind.
- Pulled and ran Vagrant image for systers portal on local machine.
- Created and configured a sample django project in Virtual Machine.
- Went through models and relationships between models in django.
- Followed github tutorials.
- Created models that were decided last week.
- Tried deploying django project on apache server.
- Forwarding port in VM , apache server runs on port 80 in VM, not able to see django application running in web browser on local box.
- Configuration settings.
- Not yet.
- Yes, addressed the problem to mentors.
- N/A
- In the coming week I will add edit user profile and change password functionality
- Behind.
- Configured the local environment for development
- tried a sample django project in VM
- Read about PEP8 and django admin app.
- Modified models that were created last week.
- Created registration,login,logout,edit profile,change password functionality,All of the code can be found here
- This code still has some issues and is to be reviewed by mentors.
- Added simple Css
- Configuring django-allauth which has signup,login,logout, password change functionality
- Pending model reviews.
- By creating dummy models to test the implemented functionalities.
- We have a meeting tomorrow and hopefully all of the issues will be resolved
- Yes
In the coming week I will add superadmin page and edit organization profile functionality
- Behind
- Configured django-allauth
- Implemented register,login,logout,change password,reset password,change email using django-allauth
- Edit User Profile,Show user Profile, Show members for a community
- Basic Super Admin Dashboard with add community, edit community profile, edit organization profile functionality
- Added Css
- Made a pull request for these changes
- Looking into django-cms for dynamically creating pages
- N/A
- N/A
- N/A
- N/A
- In the coming week I will add more functionalities to super admin dashboard
- A little behind
- Changes in models and Registration PR based on comments
- Resource Area for communities and admin access to it.
- Configured django-cms to allow admins to create dynamic pages for their communities.
- N/A
- N/A
- N/A
- N/A
- In the coming week I will add more functionalities to super admin dashboard
- Behind. Due to some circumstances suddenly had to travel this week , I will catch up in next week
- Added Tests for models
- Resource Area for communities and admin access to it.
- N/A
- N/A
- N/A
- N/A
- Add more functionalities to super admin dashboard and make communities resource area editable by admin.
- Behind.
- Add,delete,Update News for all Communities
- Add Page functionality for community admins
- Customizing django cms toolbar
- No
- Looking into django-cms docs
- No
- Design URLS
- Add,delete, update for Resource Model
- Add Unittest for add,delete,update for News and Resource
- A little Behind.
- Show All news about a community
- Show a particular news about a community
- Redirect user to profile page after login and register
- Unittests for view user profile, edit user profile
- Unittests for add,delete,update,show news for a community
- Add Page functionality for community admins
- Design URLS
- Design of main page of community(Community Story)
- Allowing non staff users to be able to edit content through django-cms front end
- No
- Looking into django-cms docs, google
- Yes
- Add,delete, update,show for Resource Model
- Add Unittest for add,delete,update,show for Resources
- A little Behind.
- Show All resources of a community
- Show a particular resource of a community
- Edit,delete,Add resource of a community
- Unittests for each of above fucntionality
- Worked on permissions for community objects with Ana Balica and came up with final set of permissions
- Started with new community request proposal form, cleared requirements for new community request proposal form
- Creating dynamic forms in django
- No
- Looking into django forms, google
- Yes
- Add,delete, update,show for Community Page
- Add Unittest for add,delete,update,show for Community Page
- Form for requesting new community
- A little Behind.
- View Page
- Edit Page
- Add Page
- Delete Page
- Manage pages for community contributors
- Main page for communities
- Permissions for each function
- Comments section for News and Resources
- Added Social media sharing buttons for news and resources
- Creating dynamic forms in django
- No
- Looking into django forms, google
- Yes
- Unittests for add,delete,update,show community Page
- Uninitests for community main page, comments , social media sharing
- A little Behind.
- Comments section for News and Resources
- Added Social media sharing buttons for news and resources
- Fixed some bugs in demo branch.
- Had systers portal demo with Rose
- Reviewed the timeline with Ana and cleared the left requirements with rose.
- N/A
- N/A
- N/A
- No
- Unittests for add,delete,update,show community Page
- Uninitests for community main page, comments for news and resources, social media sharing
- A little Behind. This week I got back to my college , so could not do much , will catch up next week
- Added monitor and unmonitor for news and resources functionality.
- Join Community , leave community , cancel request functionality for users.
- Approve join request by Community admins.
- Notification email to user when join request is approved.
- Unittests for all the functions.
- Testing and Bugfixing.
- N/A
- N/A
- N/A
- No
- Bug Fixing
- Documentation
- OK
Documentation
- Project Requirements
- Setup and Install
- User Interface Design
- Development
- Database Design
- Initial Docs
- Main Concepts
- Future Ideas
Outreachy Interns
GSoC Students